A logistical look at microservice style applications created at scale from practical experience. Purpose is to present the strengths and purpose of microservice solutions to empower teams working with them or considering them for their projects. Technology will include JavaScript and Java solutions in examples. Hosting concerns will include self-hosted and cloud considerations. Some attention given to comparison to standard or monolith solutions, but not much. Q&A by design as part of this talk. Willing to refine the scope and focus to fit conference leadership preference. Target Audience: developers, architects, managers, and teams working in or considering microservice architecture for their projects.

1. When Your Applications Work As a Team
LED BY
Nathaniel Francis
SESSION

2. NATHANIEL FRANCIS
SPEAKER AT ITB2023
Basic info’s in the bio, but here’s a few random facts
• Lorem ipsum dolor (just kidding)
• Homeschooled until high school
• Flat roofer earlier in life
• Big Star Wars fan
• Musician (piano first, then guitar)
• I really like memes (buckle up)
• Ah yes, the red glasses
• CF developer by birth, semi-
polyglot by force

3. The Microservice Approach
We’re not talking about this…

4. The Microservice Approach
Or this…

5. The Microservice Approach
The right tool for the right job

6. The Microservice Approach
Most projects start like this

7. The Microservice Approach
Grow into something like this

8. The Microservice Approach
And eventually become this
(this is a monolith)

9. The Microservice Approach
Here’s an alternative
(microservices)

10. The Microservice Approach
When is this the right tool?
When is this the right tool?

11. The Microservice Approach
Personal Example 1: Long User Experience
(11-14 seconds)

12. The Microservice Approach
2 Microservices
(~300ms)
(~7s)

13. The Microservice Approach
Advantage: scale to the need

14. The Microservice Approach
Which turned out to be more like…

15. In this case…
The Microservice Approach
This was too slow & cumbersome
This provided a much better
experience for the user & the business

16. The Microservice Approach
When is this the right tool?
When is this the right tool?

17. Basic Guidelines
The Microservice Approach
Make your applications distinct
by clearly defined functionality
Processes and data are “handed off”
very loosely coupled
“Application” is the sum total of the parts
(inner applications)

18. Let’s look at a
(really) simple
example
The Microservice Approach

19. The Microservice Approach
Since
naming
things is
hard…

20. Yes, I really did that
The Microservice Approach

21. The Microservice Approach
The “inators”

22. Accessinator
The Microservice Approach
Represents the access/entry point
into a microservice ecosystem.
The “front door” if you will

23. Savinator
The Microservice Approach
Represents data processors
of various types

24. Reportinator
The Microservice Approach
Represents data access layers like
reports, output streams, or search

25. Interface is a simple text field
(which has never been done before)
The Microservice Approach

26. Code Sample Time!
The Microservice Approach

27. The Microservice Approach
Personal Example 2: The Blender

28. Problem:
The Microservice Approach
Too many concerns on the original

29. Solution:
The Microservice Approach

30. Blender Workings…
The Microservice Approach

31. Common Thread:
The Microservice Approach
In both real-world cases,
the original product developed in such a way
that was either:
In such a way that broken down, distributed, decoupled
microservice application functionality fixed the identified
problem
too slow or
over-stressed

32. This does NOT mean:
The Microservice Approach
microservices
are
perfect

33. The Microservice Approach
Conclusion: The right tool for the right job

34. THANK YOU
Thanks to our sponsors