SESSION TITLE
Monoliths to MicroServices - Architecture patterns and migration principles
SESSION THEME
DevOps
SESSION OVERVIEW
When migrating a monolith to a microservices based architecture, it is usually easy to do what is required. However, it is tough to not do what is not required.
Teams struggle to manage the incidental complexities related to:
1) Structured Composition, because of a procedural approach
2) Centralized data
3) Concurrency
We need alternatives to these conventional techniques.
Taking the Apache HDFS (a popular and accessible open source) NameNode module as an example, the demo would discuss the alternative principles which simplifies the development of microservices.
SESSION AGENDA
Introduction to Microservices
Discussing each challenge, with examples from Apache HDFS
Discussing solutions to each challenge
Conclusion
Q&A
SESSION TAKEAWAYS
How to develop/migrate to MicroServices
DURATION
45 Mins
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
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
