The document discusses how to design microservices for an application. It explains that microservices should contain independent and similar pieces of functionality that can run in any order, unlike monolithic enterprise applications where components depend on each other in a specific order. The document then uses a search engine as an example, showing how the requirements can be broken down into independent microservices for querying, retrieving details, and handling synchronous vs. asynchronous requests.

1. Designing Microservices
A visual language
for product description
Richard Rodger
@rjrodger

3. Depends on

4. Depends on
different
things

5. Depends on
different
things
in the right
order.

7. Independent

8. Independent
similar things

9. Independent
similar things
in any order.

10. Enterprise Software

11. Depends on
different
things
in the right
order.*uml-diagrams.org
Enterprise Software

12. Microservices

13. Microservices
Independent
similar things
in any order.

14. How do you decide which
microservices to build?

15. Requirements
Messages
Services

16. "Build a search engine!"

17. Requirements
a) enter search query and get results
b) get more information about a result

18. a) do-query
b) get-details
Requirements
a) enter search query and get results
b) get more information about a result
Messages

19. Services
a) ui sends do-query to search
b) ui sends get-details to info
Requirements
a) enter search query and get results
b) get more information about a result
a) do-query
b) get-details
Messages

22. When do you need an answer?
Now: synchronous
Never: asynchronous

23. A Search Engine
in Microservices
Independent
similar things
in any order.

24. Independent

25. similar things

26. in any order.

27. A Search Engine
in Microservices

28. bit.ly/taomicro
@taomicroservice

29. Thanks!
Richard Rodger
@rjrodger