https://phpc.tv/videos/watch/c9dbd2f2-b877-4afd-9c0e-0759c5a4a9a7 When faced with a challenging legacy code base, tightly coupled and void of discernible structure: a big ball of mud, it is common to decide to refactor this monolith to a microservice architecture to separate concerns and split the codebase up, however without any clear boundaries you are in danger of creating a distributed big ball of mud. You may recognise the symptoms of a distributed ball of mud: a large unfocused 'common' library shared between multiple services; performance issues as your front end makes calls to multiple back end API's to serve a single request; dependency hell on deployments as you have to release multiple code bases simultaneously and uptime issues as a single microservice going down brings down your entire application. In this talk I'm going to cover some of the common pitfalls you might encounter when building a microservice architecture and show you how to use an event driven architecture to build truly scalable microservices. Tue, 14 Apr 2026 21:30:57 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://phpc.tv https://phpc.tv/lazy-static/avatars/a00c380b-7291-4db3-b239-61999888fbca.png https://phpc.tv/videos/watch/c9dbd2f2-b877-4afd-9c0e-0759c5a4a9a7 All rights reserved, unless otherwise specified in the terms specified at https://phpc.tv/about and potential licenses granted by each content's rightholder.