Title: How (not) to build MicroServices

1. How (not) to build
Microservices

2. Industry 4.0 – The digital
enterprise

3. The ABC
Technologies
• A is for Artificial Intelligence
• B is for Big Data
• C is for Cloud Native

4. • Elastic
• Containers
• MicroServices
Cloud Native

5. A few good Monoliths

6. Apache HDFS
1. Master/Slavearchitecture
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 datanodes
only

7. Some Observations

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

9. Side Effects!

10. Dependencies
100+ external dependencies
20+ users

11. Centralised Data
INode: In memory
meta-data

12. How To
Functional
Segregated Data
Structured
Centralised Data
How Not

14. A suitable language
C C++ Java JavaScript Python Scala Erlang
Functional
Composition
Low Low/Partial Partial Good Partial Good Good
Type System Static Static Static Dynamic Dynamic Static Dynamic
Reactive
Extensions
Not
Available
Available Available Available Available Available Not
Required
Microservices
framework
Low Low Good Good Moderate Good Moderate
Libs/tools/fw Moderate Moderate Good Good Good Low Low
Popularity High High High Moderate Moderate Low Low

15. The good parts

16. Some Functional
Programming

17. Summary
• Dependencies
• Central, free-for-all data
• Functional Composition
• Multi-paradigm language
• Good parts
• Functions as objects
• Weak typing
• Lambdas
• Functional Programming Extensions

18. Thank You