Explore the journey of transforming a monolithic software architecture into microservices from a startup perspective in this 36-minute conference talk by Susanne Kaiser, CTO at Just Software. Gain insights into the challenges and processes involved in splitting an organization into smaller teams and dividing a collaboration solution into single smaller apps. Learn about key concepts in modeling microservices, including identifying bounded contexts, extracting web apps, business logic, and data storage. Discover the complexities and benefits of implementing microservices, along with essential components such as security, service discovery, load balancing, and monitoring. Understand the lessons learned and key takeaways from this startup's transformation experience, providing valuable insights for organizations considering a similar architectural shift.
The Journey to Microservices from a Startup Perspective
Overview
Syllabus
Intro
Each journey is different
After an evolving while ...
Separate Collaboration Apps
Small, autonomous teams
Microservices come with complexity
Challenges of transformation
Transformation process
Key concepts of modelling Microservices
Identify Bounded Contexts
First approach as a co-existing service
Heavy undertake if you do all at once
Extracting Web App
Extracting Business Logic
Extracting Data Storage
Which one first?
Stop feeding the monolith
Security: Auth-Server with API-Gateway as Token
Service Discovery w/ Spring Cloud & Eureka
Dynamic client-side Loadbalancing w/ Ribbon
Design for Failure w/ Hystrix
Monitoring w/ Hystrix Dashboard & Turbine
Current ecosystem so far.
A lot to cover to establish a Microservices ecosystem
Lessons learned
Summary
Taught by
GOTO Conferences
