Yeah, I found the article to be a little annoying in that it's mostly attacking WeWork. My recommendation for anyone new to the area, is the streaming systems

Yeah, I found the article to be a little annoying in that it's mostly attacking WeWork. My recommendation for anyone new to the area, is the streaming systems book: http://streamingbook.net/ http://streamingbook.net/, which came after two excellent blog posts: https://www.oreilly.com/radar/the-world-beyond-batch-streaming-101/ https://www.oreilly.com/radar/the-world-beyond-batch-streami..., and https://www.oreilly.com/radar/the-world-beyond-batch-streaming-102/ https://www.oreilly.com/radar/the-world-beyond-batch-streami... Basically, if you have an unbounded data problem, and you might have something that is _practically_ unbounded, that book really helped me gain insight to describe what we used Kinesis for (which is really similar to Kafka in a lot of ways). Thinking about event vs processing time, ordering and windowing requirements, etc, were really helpful in thinking about my own data problems. In the end, the author of this article claimed that WeWork just simply didn't have much of an unbounded data problem. Which I generally agree with. But simply saying "you can do this in PostgreSQL" isn't really a great takeaway, and, it really feels that was the message being reinforced here.