Microservices vs The Distributed Monolith - Chris Riley
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.
4 views
14
5
6 months ago 07:06:32 1
.NET Microservices – Full Course for Beginners
6 months ago 00:04:05 3
Винни Пух vs PanjabiMC Al mix
6 months ago 00:44:54 1
Expert Talk: Are We Post-Serverless? • Julian Wood & James Beswick • GOTO 2024
6 months ago 01:39:26 1
AMD Zen 5 Specs Confirmed, Intel Arrow Lake, FSR 3.1, PS5 Pro, Nvidia Blackwell | Broken Silicon 250
7 months ago 00:04:28 1
The Legend of Zelda: Breath of the Wild | Cemu Vs Yuzu Vs Ryujinx | Steam Deck
7 months ago 00:40:52 1
Patterns of Distributed Systems • Unmesh Joshi & James Lewis • GOTO 2024
7 months ago 00:49:39 1
There’s No Such Thing As Plain Text • Dylan Beattie • YOW! 2023