Distributed systems antipatterns by Thoughtworks published on 2018-09-15T15:33:42Z The tech landscape has changed fundamentally, with the growth in distributed computing and microservices. But it's not always easy to create truly independent services, especially amid time and budget pressures — sometimes it's just easier to allow multiple services to use a shared database. In this episode, our panel explore the antipatterns we've seen emerge and consider how we can avoid them. Genre Technology Comment by Neil Barnwell I must respectfully disagree about CQRS's perceived "complexity". People are getting it wrong because they wrongly think to be doing it "correctly" it has to be this huge complex architecture with events and queues and databases and things, but really it's not. It's just separating the architecture (note the lower-case 'a') of the things responsible for handling commands from the things responsible for returning data for queries. The trick is that once you have taken that first very simple step, various interesting options open up for you. 2018-09-20T17:04:23Z Comment by diathesis There's an odd but mildly interesting background noise that makes it sound like you're podcasting from within a giant fish tank with an aeration system. 2018-09-19T19:58:48Z