Botching your Microservices the easy way
|Architecture & Security|
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. And I will show you techniques, that some guys will try to make Microservices succeed, so you can avoid those!
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 - Security and load testing can be ignored, Microservices scale anyway! - Polyglot is fun...especially when you need to debug stuff - ...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.
I am a Principal architect at Senacor Technologies with a history of + 14 years of working in various projects using a bunch of different stacks, environments and processes. Although a techie at heart, I realize that a project can only succeed with the right people and the right mindset.
My current focus is on building agile and modern organizations and architectures, such that our customers can cope with the challenges of the digital age.