1.
Microservice Architecture
Over the rainbow
Vincenzo Carlino <v.carlino@mvlabs.it>
Steve Maraspin <s.maraspin@mvlabs.it>
Codemotion Online Tech Conference - Italian Edition Spring 2022 - 23/03/2022

2.
VINCENZO

3.
STEVE

4.
Microservices since 2017

5.
DEPLOYMENT EXAMPLE

6.
ANOTHER DEPLOYMENT EXAMPLE

7.
How do we handle authentication & ACLs?

8.
AUTH

9.
AUTH 2.0

10.
Global Authentication & Authorization Service

11.
Global Authentication & Authorization Service

12.
Global Authentication & Authorization Service

13.
Global Authentication & Authorization Service

14.
Auth 3.0

15.
Auth 3.0
Not a shared
database!

16.
Auth 3.0

17.
Auth 3.0

18.
Auth 3.0

19.
Auth 3.0

20.
Auth 3.0

21.
Auth 3.0

22.
Auth 3.0

23.
Auth 3.0

24.
How are logged users affected?

25.
Logout

26.
Workflow?

27.
User

28.
User Group

29.
User
Work Order
Group

30.
User
Work Order
Group
Inspection

31.
Orchestration VS Choreography
● Choreography can maximize fan-in,
as services react to events independently

32.
Orchestration VS Choreography
● Choreography can maximize fan-in,
as services react to events independently
● Orchestration allows a client to handle & centralize a workflow
Orchestrator can be kept simple & flexible

33.
LEFTOVERS…

34.
Clear Cache
Developer

35.
Clear Cache
Developer

36.
Clear Cache
Developer

37.
Clear Cache
Developer

38.
Clear Cache

39.
Clear Cache

40.
Cross Cutting Concerns

41.
Maintenance Inspections

42.
Maintenance
logging code…
Inspections
logging code…

43.
Logging
Maintenance Inspections

44.
Logging

45.
Logging ACL

46.
https://dzone.com/articles/ms-chassis-pattern

47.
Chassis Framework
Service Template

48.
Polyglot System Consequences
● More Coding Conventions
● Duplicated Code Logic
● Additional Team Knowledge Needed
● Entropy

49.
Dealing with Complexity

50.
Debugging Microservices with Tracing

51.
Debugging Microservices with Tracing

52.
Debugging Microservices with Tracing

53.
Versioning
Tags Images Deployments

54.

55.
OBSERVABILI-TEAM

56.
Should I use them,
or should I not?

57.
Monolithic Architecture

58.
Monolithic Architecture

59.
Microservices concepts applied …

60.
WRAP UP

61.
What to Keep in Mind
• Not an all or nothing choice
– Choreography VS Orchestrator
– Microservices or Not
• A little upfront design is suggested (boundary definition)
– At later stages microservices foster agile approaches
• Conway’s Law -> Organizational impact (DevOps)
• Achieved separation of concerns, ease of deployment
• Kubernetes & related tools helped a lot!
• There are long term benefits (for complex projects)

62.
Thank you
Vincenzo Carlino <v.carlino@mvlabs.it>
Steve Maraspin <s.maraspin@mvlabs.it>
Codemotion Online Tech Conference - Italian Edition Spring 2022 - 23/03/2022

63.
@maraspin
s.maraspin@mvlabs.it
@VincenzoCarli15
v.carlino@mvlabs.it

64.
Additional Resources
FORTHCOMING

65.
Questions?
Vincenzo Carlino <v.carlino@mvlabs.it>
Steve Maraspin <s.maraspin@mvlabs.it>
Codemotion Online Tech Conference - Italian Edition Spring 2022 - 23/03/2022

66.
Join Our Mailing List
6 Messages a Year, at Most
http://eepurl.com/s3Kab
@mvlabsit
www.facebook.com/mvlabs