When I was young and took my CS classes I learned about ACID and it seemed sound and reasonable. Then I went to work and learned that it could mean different things (especially isolation…) for different database vendors… Around 2009 I’ve heard about CAP theorem - that was besides sound and rather reasonable in the brave, fresh distributed world. And then 1 after another - NoSQL vendors started to claim they’ve beaten CAP theorem (* as they realize it of course…) And late it got even more complex - stream processing engine have their notion of transactions - atomicity, isolation and so on. In this talk I will effort to make something out of this mess - we’ll look at any of definitions and effort to figure out which usage case require peculiar kind of isolation or transactionality. Of course any of it will be based on my own experience - including rather quite a few blood, sweat and tears ;)
GeeCON Prague 2019: Maciek Próchniak - Being transactional in 2019 - what does it actually mean?
When I was young and took my CS classes I learned about ACID and it seemed sound and reasonable. Then I went to work and learned that it could mean different things (especially isolation…) for different database vendors… Around 2009 I’ve heard about CAP theorem - that was besides sound and rather reasonable in the brave, fresh distributed world. And then 1 after another - NoSQL vendors started to claim they’ve beaten CAP theorem (* as they realize it of course…) And late it got even more complex - stream processing engine have their notion of transactions - atomicity, isolation and so on. In this talk I will effort to make something out of this mess - we’ll look at any of definitions and effort to figure out which usage case require peculiar kind of isolation or transactionality. Of course any of it will be based on my own experience - including rather quite a few blood, sweat and tears ;)
