Why you shouldn’t build a microservice architecture
What if the primary goal of architecture is speed? Your microservices might be slowing you down.
#1about 3 minutes
The primary goal of software architecture is speed
Good architecture and practices should ultimately save time and help you get to market faster.
#2about 3 minutes
Choosing the right architectural tool for the job
An analogy of cutting down a tree illustrates that microservices are heavy equipment only necessary for large, complex problems.
#3about 5 minutes
Questioning the actual benefits of microservices
Before adopting microservices, critically evaluate whether your project actually needs benefits like scaling individual components or supporting multiple teams.
#4about 2 minutes
A decision tree for adopting a microservice architecture
If the specific benefits of microservices do not apply to your situation, you should not adopt them because the disadvantages are guaranteed.
#5about 4 minutes
Practical advice for building a microservice architecture
Key practices for success include keeping services small, standardizing monitoring, maintaining API compatibility, and not using architecture to solve organizational problems.
#6about 2 minutes
Embrace imperfection and learn from production
No architecture is perfect, so it is better to ship quickly and get real-world feedback from production to improve over time.
#7about 5 minutes
Q&A on monoliths, serverless, and specific use cases
Discussion covers hybrid architectures, the rise of serverless patterns, and specific scenarios where microservices are a good fit, like data pipelines.
Related jobs
Jobs that call for the skills explored in this talk.
Matching moments
01:32 MIN
Choosing the right tool and managing architectural complexity
Snappy UI needs no Single-Page Application
04:42 MIN
Understanding the pros and cons of microservices architecture
Developing locally with Kubernetes - a Guide and Best Practices
02:34 MIN
The flawed debate between monoliths and microservices
Microservices? Monoliths? An Annoying Discussion!
05:39 MIN
Why heavy abstraction is not needed in microservices
Seven Myths, Three Reasons, One Goal
01:37 MIN
Why a microservices architecture is a good fit
Optimizing Your App for Success: Tips and Techniques for managing slow devices
01:39 MIN
Navigating the headwinds and barriers of microservice sprawl
Lessons from Our API Past: Evolving to a Resilient API Future
00:50 MIN
Q&A: When to build a monolith application
Strategies to accelerate SaaS Application Development
02:32 MIN
Determining when to use the micro-application architecture
Independently together: how micro-applications improve developer experience + app performance
Why You Shouldn’t Build a Microservice ArchitectureWelcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Michael Eisenbart who talks about the pros and cons of microservice architecture.About the speaker:Michael has been working for Bosch as a sof...
Chris Heilmann
Micro Components - a different approach to a simpler component-based webThere has been a lot of heated discussion lately in the web community about component based development. One side argued that Web Components are a standard we should follow whereas others complained that they still lag behind in what frameworks offer...
Eli McGarvie
Stop Wasting Time: How to Lead a Stand-Up Meeting & Get ResultsWe all know the feeling: your stand-up meeting starts… and the energy in the room slowly deflates. Eyes glaze over, minds wander. Maybe you can even see their attention drop on smartphones or laptops.Within minutes or even seconds, instead of a quick...
Benedikt Bischof
Web Development Best Practices: What The Data Tells usWelcome to the new issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Laurie Voss who gave advice about the best practices in web development. What you will learn:What’s the current state of web development - “k...
From learning to earning
Jobs that call for the skills explored in this talk.