We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Top 5 techniques for building the worst microservice system ever - William Brander - NDC Porto 2023
Learn the top techniques to intentionally build a suboptimal microservice system, including adding network calls, avoiding frameworks, and keeping services tightly coupled.
- The top 5 techniques for building a bad microservice system are: 1) adding a network call in front of everything, 2) not using off-the-shelf frameworks, 3) making sure there is high coupling between services, 4) creating a monolith, and 5) not using queues.
- Instead of building a microservice system, consider a monolith, it’s faster and more efficient.
- System quality follows a normal distribution, with most systems being OK and a few being exceptionally high or low quality.
- Being an OK programmer means writing some good and some bad systems, and it’s hard to estimate the time it takes to add functionality to a system.
- When using microservices, consider using the Strangler Fig pattern and queues to handle communication between services.
- Don’t bother estimating the time it takes to add functionality, just use linear scaling.
- With each new feature, the system becomes more complex and harder to understand.
- The worst thing is not knowing what you’re doing, so just use a framework and pretend.
- Microservices are not the answer to all problems, but can make things worse.
- But, if you want to build a bad microservice system, just add a network call in front of everything and you’re done!