Download to read offline
More Related Content
Similar to Microservices: Another Way
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
Microservices: Another Way
- 1.
- 2. INTRODUCTION 13 Distributed & Highload CloudSolutions WorkExperience Languages Focus
- 3. AGENDA Is Monolith areal problem? Why Micro-Services? How we gonna do Micro-Services? Why Service Fabric? What is Another Way?
- 4. IS MONOLITH A REALPROBLEM?
- 5. MONOLITH Azure AWS Desktop Browsers 80% backend logic20% backend logic Monolith
- 6. MONOLITH - SCALABILITY 80%backend logic Azure Redis: Cache Redis: WebSockets Backplane SQL Store Monolith Instance 1 Monolith Instance 2 Monolith Instance 3 Monolith Instance N Stateless & Scalable Redis SQL – limited scale – 10% load
- 7. PROBLEM - TECHNICAL 1Language / Platform limitation Module cannot be scaled separately DB Schema sharing
- 8. PROBLEM - BUSINESS Acquiringseveral companies Expecting growth ~ x5 in a year Targeting for Hybrid solution
- 9.
- 10. SCALING & HARDWARE ~20 Modules 3 – High Load 1 – requires Memory GPU Module 1 GPU Module 2 SSD Module 1 SSD Module 2 Node with SSDNode with GPU
- 11. LANGUAGE & TOOLS Useappropriate language & tools for component goals Languages: Java .NET NodeJS Ruby C++ Python Storages & tools: SqlServer MySql Redis ELK Kafka Apache Solr Apache Spark
- 12. HYBRID (CLOUD +ON PREMISES) Cloud Service 1 Service 2 Data Service 1 Data Service 2 Service 3 Regular Tenants Classified Tenants Tenant DC
- 13. HOW WE GONNADO MICRO-SERVICES?
- 14.
- 15. REQUIREMENTS - DEVOPS Scriptminimization Upgrade in single command High Availability & Self-Healing Service Discovery Hardware Constraints
- 16. DEPLOYMENT – SERVICEPER VM
- 17.
- 18.
- 19. WHY WE CHOSE SERVICEFABRIC?
- 20.
- 21. SERVICE FABRIC vsCONTAINERS ORCHESTRATION Service Fabric Containers Orchestrating Services Containers Ops Cost Low Medium App Infrastructure One SDK Custom Scaling Instance + Partitioning Instance Service Isolation No, Container, Kernel Container
- 22. Service Fabric Cluster Node 1 Node5 Node 3Node 4 Node 2Resource Manager Cluster Manager Naming Service Image Store Health Manager CLUSTER
- 23. Service Fabric Cluster Node 1 Node5 Node 3Node 4 Node 2 Manage Admin UI PS / CLI Application Web Service Worker Service Deploy Web Service Web Service Web Service Worker Service Worker Service Worker Service Worker Service Worker Service MANAGEMENT
- 24.
- 25.
- 26. PROGRAMMING MODELS Reliable Services Stateful Stateless Actors SDK No SDK Containers Guest Executable
- 27. RELIABLE SERVICES Cluster State StatelessStateful State
- 28.
- 29.
- 30.
- 31. WHAT IS ANOTHERWAY?
- 32. ORCHESTRATING / SCALING/ SELF-HEALING Usually Another Way Resource Manager Failover Manager Health Manager
- 33. SERVICE DISCOVERY Usually AnotherWay Eureka Naming Service
- 34.
- 35. LOAD BALANCING Ribbon Usually AnotherWay Naming Service Reverse Proxy
- 36. STATE Usually Another Way ReliableCollections
- 37. HEALTH / MONITORING Eureka UsuallyAnother Way Health Manger
- 38. TESTABILITY Usually Another Way FaultAnalysis Service
- 39.
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47. WHEN TO USE Youwant to try Another Way
- 48. LIMITATIONS Hyper-V Virtualization –Q3 201 Full Linux support – Q4 2017 Stateful services on Linux – Q4 2017 Reverse Proxy on Linux – Q4 2017 Docker Compose support – Q4 2017 Heterogeneous Cluster – Q1 2018
- 50.
Editor's Notes
- #48 Hybrid Application – Cloud + OnPrem Application must be hosted on Azure Lots of Programming Languages Minimize SysOps / DevOps workload Simplify migration from Monolith Heterogeneous Cluster (Future) – Windows + Linux