Monolith to microservices journey
- 1. Journey
- 2. Hello! I am Pandian Velayutham Principal Software Architect @ Medhost Inc., 2
- 3. monolith > microservices this must be 1,000,201 times you hear this 3
- 4. “Any fool can write code that a computer can understand. Good programmers write code that humans can understand. - Martin Fowler 4
- 5. “If you can't build well structured monolith, what makes you think you can build a well structured set of microservices - null 5
- 7. monolith 7 difficult to scale long build/test/release cycles operations nightmare architecture hard to maintain & evolve new releases take months long time to add new feature lack of agility lack of innovation lack of customer satisfaction
- 9. ● Manageable service - faster development/easier to maintain ● Independent development ● Removes barrier to adopt new Technology ● Easy to build and deploy - CD possible ● Each service can be scaled independently what can it solve? ● Add complexity - distributed system (partial failure) ● Partitioned database (RDBMS to NoSQL) ● Testing microservices (integration) is difficult - need all related services ● Careful plan and coordination needed when delivering multiple services ● Deployment needs orchestration (which adds complexity) 9
- 10. process lift and shift to cloud move monolith into EC2 with infrastructure components. split services split into microservices. security first. follow microservices principles. Infrastructure as code change mindset of developers. no one will create infrastructure, make them learn cloud with automation tool. 10
- 11. architecture do we really need this? 11
- 12. 12
- 13. ● Running 45 microservices in development laptop? - shared environment (docker-compose) ● How to monitor log? log-io ● Version madness - common base project (similar to springboot) ● Still need frameworks (custom/shared) Development challenges? ● How to support at least 3 versions? 3 shared development environments ● How to share ssh access? Vault ● Empower developers to add microservices - traceability ● Empower developer to make configuration changes - with traceability 13
- 14. ● Order of deployment - make sure to remove dependencies at early stages ● Controlled CD pipeline - approval model ● Blue-Green deployment ● Manual tasks - automate as much as possible Release challenges? 14
- 15. ● You develop you manage - change mindset ● Add service monitoring and self healing ● Add synthetic monitoring ● Log aggregator ● Integrate with messaging tool ● APM is critical ● Auto scaling is really hard - keep monitoring and adjust ● Serverless is key Operational challenges? 15
- 16. Finally ● Challenges with Monolith to microservices development ● Challenges with container orchestration ● Challenges with development setup for developers when you have 40+ microservices ● Challenges with “you build you run” ● Challenges with multiple environment management (infrastructure as code) ● Finally HIPAA 16
- 17. Thanks! Any questions? You can find me at: ● @sivalingapandia ● https://www.linkedin.com/in/sivalingapand ian-velayutham-704110a6/ ● sivalingapandian.velayutham@gmail.com 17