Distributed systems antipatterns
Thoughtworks Technology Podcast
Thoughtworks
4.5 • 58 Ratings
🗓️ 13 September 2018
⏱️ 27 minutes
🧾️ Download transcript
Summary
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.
Transcript
Click on a timestamp to play from that location
| 0:00.0 | Welcome to ThoughtWorks podcast. This is Neil Ford. |
| 0:05.7 | And this is Mike Mason. And we're here actually in the middle of creating a new technology radar. |
| 0:11.5 | And we're here with three of our Doppler colleagues who are part and parcel to the creation of the radar. |
| 0:18.1 | Scott Shaw. Despite my accent, I'm from Australia. |
| 0:20.9 | I've lived here for many years, and they had a technology for ThoughtWorks in Australia. And I'm Evan Botcher. I'm a technical principal out of Melbourne, in Australia. They're both bright-eyed because they didn't have to travel because we're currently in Sydney. And so this is one of the rare chances that they're not jet lagged, and we. And a shihar from China. So I'm the |
| 0:39.0 | hydrothanology of thorough China. So one of the interesting topics that came up yesterday as we |
| 0:44.2 | were putting together the radar are all these topics around distributed computing and messaging |
| 0:49.6 | and events. And so, and a lot of those topics came up as too complex to blip because they're too |
| 0:55.2 | nuanced. But there was a lot of interesting conversations there. So that's why we're here this |
| 0:59.6 | morning. And I think we started this thing by talking about distributed model lists. Wasn't that |
| 1:04.2 | right? I think so. That was a term that came up. I never heard anybody use it before, but somebody |
| 1:09.5 | brought it up to describe |
| 1:11.5 | systems, even though they're distributed, they're distributed across several different processes. |
| 1:17.4 | They actually are tightly coupled together, those processes and have to be deployed, tested, |
| 1:23.0 | and operate as one thing. |
| 1:24.9 | That's actually a term that we looked up. |
| 1:26.8 | It's a real term out of the world, right? |
| 1:28.7 | We didn't just make that up. I've seen a lot of them anyway. They're definitely common. |
| 1:35.5 | Yeah, yeah. It happens a lot. I've seen, you know, microservices projects start out with the |
| 1:41.7 | intent of keeping everything decoupled, but gradually it gets |
| 1:45.3 | when they're under pressure, they're under time pressure to get things done. They cut corners and |
| 1:51.5 | they start reaching in and pulling data directly out of each other's databases and that creates |
... |
Please login to see the full transcript.
Disclaimer: The podcast and artwork embedded on this page are from Thoughtworks, and are the property of its owner and not affiliated with or endorsed by Tapesearch.
Generated transcripts are the property of Thoughtworks and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.
Copyright © Tapesearch 2026.