Monoliths to Microservices - Architecture patterns and migration principles (my presentation at Agile Gurgaon 2018)

1. Monoliths to Microservices
Migration Principles

2. Architecture

3. Apache HDFS
1. Master/Slave architecture
2. Name Node manages meta data
3. Single Name node simplifies the
architecture
4. Name Node takes care of allocation,
replication, backup
5. User data flows through data nodes
only

4. Design

5. backup
cache
checkpoint
FSImage :
persistence of
metadata
INode: In
memory
metadata
Design

6. Dependencies

7. Dependencies
100+ external dependencies
20+ users

8. Centralized Data

9. Centralized Data
INode: In memory
meta-data

10. Mutability

11. Microservices
Functional
Segregated Data
Simply Concurrent
Structured
Centralized Data
Managed Mutability
Monoliths

12. The good parts

13. Segregated Data

14. Simply Concurrent

15. Simply Concurrent

16. Summary

17. Summary
C C++ Java Node.js Python Scala Erlang
Functional
Composition
Poor Poor Partial Good Partial Good Good
Type System Static Static Static Dynamic Dynamic Static Dynamic
Concurrency-
Complexity
Complex Complex Complex Simple Complex Moderate Simple
Concurrency-
Mutability
Mutable Mutable Mutable Mutable Mutable Separation
of values &
variables
Immutable
V.Scaling Good Good Moderate Moderate Good Moderate Good
H.Scaling Moderate Moderate Moderate Good Moderate Moderate Good
Reactive
Extensions
Not
Available
Available Available Available Available Available Not
Required
Microservices
framework
Poor Poor Moderate
(Vert.x)
Good
(Express
based)
Poor Moderate Moderate
(Elixir)
Libs/tools/fw Poor Moderate Good Moderate Good Good Moderate
Popularity High High High Moderate Moderate Low Low

18. Thank You
agileiq.blogspot.com