2. Who is this Guy? (Lior Bar-On)
SAP: microservices-inspired architecture, to ease code maintenance
Gett: 24 microservices, 18 created in the last year
Developer, Architect, Chief-Architect
תוכנה ארכיטקטורת בלוג
Career
Microservices
Blogger
12. We do Microservices too - like everyone else!
Remember:
No Software Engineer was ever got fired for
implementing ALL Microservices-related
Patterns to the system.
Though, they may get fired for not delivering
Business Value within a reasonable time.
25. MSA is about Dev Org’s Scalability
● Services are small enough for code not to become ugly / lose control
The number of services scale with the System’s growth
● Services are small enough to be sometime fully re-written
26. MSA is about Dev Org’s Scalability (2)
Fences make good neighbours
Not-Sharing Memory makes fewer “dependency breaches”
Now: Cross-Service APIs - are what you need to watch!
- למודולים ברורה חלוקה לנו יש במונוליט
זמן לאורך ולהתפזר אותה להפר קל אבל יותר יש אזי APIs ו רשת בתקשורת מגובה החלוקה כאשר ,MSA ב
פעמיים לחשוב גם לנו שעוזר מה - נוספים תקשורת קווי ליצור עבודה
.הסדר על ולשמור
27. Seriously:
Microservices have downsides too:
● The “Whole Picture” now shattered and you need to re-assemble it
(monitoring, logs, business logic needs, etc.)
● Network sensitivity
● Development overheads; Performance overheads.
28. Seriously:
Consider a “Monolith First” approach (a best-practice!)
Remember microservices are new. Question everything!
Make your own variations!
Allow yourself using non-microservices architecture
E.g. facebook, etsy, etc.
31. … to make a better use of it
בעיה של נכונה התאמה עם
עמוקה הבנה מתוך ועבודה ,לפתרון
מוצלח למימוש הסיכויים גדלים -
!מיקרו-שירותים של