19. Replaceability
> Small components hard to mess up
> Each module can be replaced
> …small green field project
> ...different technology stack possible
24. Build Pipeline for
Microservices
> Build pipeline per Microservice
> Smaller
> Easier to set up
> Less features (3rd party systems)
> Faster Feedback: Less tests
42. Refactorings
> Move code to a new service: Easy
> Move code from service to service
> Might be a port to a different language
> Hard
43. Global Refactorings
> Really hard: Global restructuring
> i.e. moving everything to a different place.
> …but that is always hard…
> ...and the result of a major screwup.
> Do you want to optimize for this?
44. Many New Technologies
> Microservices framework
> Service discovery
> Routing / API Gateway
> Continuous Delivery pipeline
> Docker
> Docker scheduler (Kubernetes)
> ....
61. Layered: Issues
> Changing a business process cause many
changes
> …in Frontend and many backend
> Lots of communication between teams and
components
86. Conclusion
> Microservices are a set of architecture
decision
> Architecture is about trade-offs
> Architecture is different for each project
> Go beyond microservices by picking the
best decisions!
> …and gain most benefits