The document discusses some of the challenges of using microservices for applications. It found that communication between microservices is difficult due to issues like latency, eventual consistency, and large data requests. It recommends designing microservices with these communication challenges in mind from the beginning, including thinking about APIs, data duplication, filtering, versioning, and deployment processes. Automating deployments, service discovery, security, and monitoring are also important aspects to consider when using microservices.

1. Microservices:
the nitty gritty

2. I did a project with
microservices

3. "Just
use
microservices"

4. and it went well
for the first

5. and it went okay
for the second

6. it started to get hard
on the third

7. what did we find?

8. communication
is
hard

9. HTTP + REST

10. large conversations

11. myapp.com/customers
GET

12. {
"customers" :
[
{
"name" : "igloocoder",
"address" : "123 Main St.",
"active" : true,
"premium" : true
},
{
"name" : "Apple",
"address" : "1 Infinite Loop",
"active" : false,
"premium" : false
}
]
}

13. only need name and
premium?

14. basic APIs won't cut it

15. myapp.com/customers?fields=name,premium
GET

16. {
"customers" :
[
{
"name" : "igloocoder",
"premium" : true
},
{
"name" : "Apple",
"premium" : false
}
]
}

17. filtering

18. /customers/active
/customers/premium

19. can't expect
client side action

20. give succinct answers
to large conversations

21. service-to-service
communications

22. update/delete/create

23. reading data is harder

24. reading data is harder

25. latency

26. REST favourable

27. going to want
filtering and partial response

28. denormalize

29. embrace data duplication

30. keep data close

31. sync via events

32. embrace
eventual consistency

33. every microservice
is a separate app...

34. every microservice is a
separate deployment

35. how do you deploy
so many apps?

36. automation

37. what environments?

38. 1 monolith
==
10/20/50/100? microservices

39. upgrades?

40. avoid
lock step deployments

41. challenges

42. some client
Our API v1
Our API v2

43. service location
&
config mgmt

44. where is that damn thing?

45. <add key="myService"
value="http://...."

46. Zookeeper/Consul

47. securing things

48. token based auth

50. Think about things
from the beginning

51. Usability?

52. Versioning?

53. Deployments?

54. Develop these
capabilities first

55. build for the cloud

56. engage DevOps
from the start

57. Things we didn't talk about
Handling communication volatility
Logging & Monitoring
Distributed System Fallacies

58. Thank you
donald.belcham@particular.net
@dbelcham
www.igloocoder.com/tags/microservices
www.github.com/dbelcham/microservice-material