This document summarizes a session on microservice architecture. Some key points covered include: - Netflix implemented microservices independently and component-based for scalability. Other platforms can also take advantage. - Microservices allow gradual migration from monolithic architectures by creating wrappers for each layer. This is a more suitable approach. - Netflix open source projects like Eureka, Hystrix, Ribbon, and Zuul help with service registration, latency/fault tolerance, load balancing, routing, and other capabilities. - Spring Cloud Configuration uses Git for dynamic REST API configuration changes. - Several anti-patterns of microservices adoption are discussed, such as seeing them as a "magic pixie dust" or focusing

1. Micro Service Architecture -
Session 2
Amin Arab
Tosan
Tir 98
https://www.linkedin.com/in/amin-arab-a653b13a/

5. •‫ارائه‬ ‫براساس‬ ‫ارائه‬ ‫این‬Component‫معماری‬ ‫های‬Netflix‫انجام‬ ‫مستقل‬ ‫صورت‬ ‫به‬
‫شود‬ ‫می‬.‫چون‬
•‫سایر‬ ‫کنار‬ ‫در‬ ‫اجزا‬ ‫این‬Platform‫شود‬ ‫می‬ ‫استفاده‬ ‫هم‬ ‫ها‬.
•‫الیه‬ ‫ایجاد‬ ‫برای‬Wrapper‫معماری‬ ‫روی‬ ‫بر‬Monolithic‫به‬ ‫گام‬ ‫به‬ ‫گام‬ ‫مهاجرت‬ ‫و‬Micro
Service‫است‬ ‫تر‬ ‫مناسب‬.

6. Netflix OSS
- Eureka (Service Registry and Service Discovery)
- Hystrix (Latency and Fault Tolerance)
- Ribbon (Load Balancing)
- Zuul (Edge Service and Routing)
- Dynamic routing
- Monitoring
- Resiliency
- ,……… there are too many

7. Spring Cloud Configuration
• Git + Spring => Dynamic Rest Configuration

9. Anti Patterns

10. Anti Patterns
• Microservices are a magic pixie dust - believing that a sprinkle of microservices will solve all of
your development problems
• Microservices as the goal - making the adoption of microservices the goal and measuring success
in terms of the number of services written
• Scattershot adoption - multiple application development teams attempt to adopt the
microservice architecture without any coordination
• Trying to fly before you can walk - attempting to adopt the microservice architecture (an
advanced technique) without (or not committing to) practicing basic software development
techniques, such as clean code, good design, and automated testing
• Focusing on Technology - focusing on technology aspects of microservices, most commonly the
deployment infrastructure, and neglecting key issues, such as service decomposition
• More the merrier - intentionally creating a very fine-grained microservice architecture
• Red Flag Law - retaining the same development process and organization structure that were
used when developing monolithic applications.

11. •‫گیری‬ ‫کار‬ ‫به‬Component‫معماری‬ ‫دانش‬ ‫هم‬ ‫به‬ ‫ها‬Micro Service‫آنها‬ ‫های‬ ‫الگو‬ ‫و‬
‫از‬ ‫مختلفی‬ ‫های‬ ‫ترکیب‬ ‫و‬ ‫روش‬ ‫و‬ ‫مسائل‬ ‫و‬ ‫دارد‬ ‫نیاز‬Component‫می‬ ‫موجب‬ ‫را‬ ‫ها‬
‫شود‬.
•‫باشد‬ ‫داشته‬ ‫شما‬ ‫معماری‬ ‫بر‬ ‫زیادی‬ ‫تاثیر‬ ‫تواند‬ ‫می‬ ‫شما‬ ‫استقرار‬ ‫استراتژی‬ ‫مسئله‬.
•‫مثل‬ ‫ماشین‬ ‫از‬ ‫استفاده‬Kubernetes‫با‬ ‫ان‬ ‫رابطه‬ ‫و‬config server‫اثر‬ ‫شما‬ ‫معماری‬ ‫بر‬ ‫تواند‬ ‫می‬
‫بگذارد‬.

12. Compare
• https://developers.redhat.com/blog/2016/12/09/spring-cloud-for-
microservices-compared-to-kubernetes/
• https://stackshare.io/stackups/eureka-vs-kubernetes-vs-openshift