No Sequel vs SQL Server

The no sequel guys came in and says, ah, you really instructed me with this tables and columns and this sequel, I hate sequel. And it does, it just doesn't fit our application. So they created everything home scratch, storage engine. For example, that's the first use case. I have a document adjacent to another document. Just store it. It's just a bunch of bite. Later they added transactions. later they added wall. Later they have indexes. They slowly added it. The API is a get in set instead of just SQL and clear separation. That's the only difference inSQL and no SQL.

Transcript

Play full episode

Remember Everything You Learn from Podcasts

Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.