3 ms·

In this case they should switch to uuidv7 or similar to have this guarantee

• aleksiy123 2y ago
  Switching IDs is going to be a breaking change across their whole product and customer base. Thats a way bigger undertaking and decision then just optimizing a single query. Like killing an ant with a Tsar Bomb.
  • throwaway28453 2y ago
    One alternative could be to add a separate column that can be used to keep track of insert order. But they would need to consider the costs before they do this, as it could impact the insert performance. The true "modern" cool kids solution would of course be to create a service that listens to WAL, inserts it into a Kafka cluster that is connected to a pipe for inserting into Elastic search. Much more fun and resumé friendly than optimizing a query. I bet the author of this blog would get a much larger audience. Bonus points if the ingestion service was written in Rust and run on a serverless platform
  • Delmololo 2y ago
    Yes and sooner this gets started the better. Otherwise it will cost more and more. Especially for a chat app!
  • Delmololo 2y ago
    Actually it's not a breaking change. You can switch the uuid generation, wait a little bit and add an.'archive' switch which will use the old and slower query when the date is old. Should definitely be helpful resource wise for a lot of people