ID spoofing

[paralleldrive]

ID spoofing

[ericelliott]

Hi Rob,

I don't see a problem with enforcing sequential IDs if you have a need for them in the context of your application. Ensuring that IDs are sequential is not the same thing as decoding the groupings to extract any semantic meaning from the ids.

For example, I would consider it unwise to extract the datestamp and use it as the entity creation time in your application, or to extract the client sequence and use it for some semantic purpose in your application. I think that enforcing sequence is in a different class.

That said, clients that are not under your control could spit any random timestamp at you. It's up to you to determine how you'll handle those cases. I'd be careful not to be too strict. There are other ways to optimize database performance. For instance, you could insert a memory cache such as Redis or Memcached in front of your permanent storage. I'm a strong believer that these sorts of performance optimizations shouldn't be too coupled to your application logic.

[RobertButera]

Thanks for the feedback.

I will probably just settle on doing some basic format (sanity) checking on the id and leave it that.

Rob

[ericelliott]

👍