Microservices are just a bunch hip new framework plus some AngularJS frontend or React, right? So, if you want to make sure that you absolutely and definitely fail at your Microservice project, then watch this talk and learn how.
Using real world experience from multiple green field and brown field projects, I can show you: - how to ignore the mandatory organizational impact - how to focus on the code only without any regard towards ops and testing - continuous deployment is for losers. Real projects use their meat cloud for delivery - jumping onto every new and untested framework is a must - EventSourcing and CQRS are both free lunches. So, you can add complexity without any real need - ...and more
If you mind my tips, then surely you will fail at Microservices and your boss will never again try to move away from your beloved vintage monolith.
86. @koenighotze#DevExperience18 #10TipsMicroservices
The network is reliable
Dependencies indicate good design, like in
dependency injection
A system stable as concrete sounds good
Synchronous dependencies are easy
What is half a system good for, anyway? So
avoid Circuit breakers
173. @koenighotze#DevExperience18 #10TipsMicroservices
Refactoring is hard, just do not do it
Maintain yet another system
Avoid internal knowledge and build
external skills
Distinguish between cool devs and
not-so-cool ones…openly
Create a hostile environment of
suspicion and distrust