The document provides a summary of microservices as an architectural style for developing applications. It describes microservices as a suite of small, independently deployable services that communicate through lightweight mechanisms like HTTP APIs. Each service runs in its own process and is built around business capabilities. There is minimal centralized management of services, which can use different programming languages and data storage technologies.

1. A Gentle Introduction
to Microservices

2. In short, the microservice architectural style is an approach to
developing a single application as a suite of small services,
each running in its own process and communicating with
lightweight mechanisms, often an HTTP resource API. These
services are built around business capabilities and
independently deployable by fully automated deployment
machinery. There is a bare minimum of centralized
management of these services, which may be written in
different programming languages and use different data storage
technologies.
-- James Lewis and Martin Fowler

3. a suite of small services, each running in its own process,
built around business capabilities and independently
deployable.
In short...

4. architectural style

5. not a technology

6. not a platform

7. not a "stack"

8. not a design pattern

9. great...they're nothing

10. but they're everything

11. they are small services

12. how small?

13. small

15. small-ish

16. sizing is hard

17. bounded context

18. aggregate root

19. encapsulated

20. isolated

21. stand alone
and
operate on its own

22. stand alone

23. each microservice gets...

24. it's own
execution process

25. WebAPI
(in its own app pool)

26. self hosted service

27. windows service

28. Azure process

29. shut down test

31. the data store

32. shut down test

33. what did it affect?

34. data store coupling

35. At least

36. maybe 2

37. or 3

38. never <1

39. each microservice
is an application

40. microservice
data
store
data
store
data
store

41. 1 microservice : 1 repo

42. isolation

43. 1 microservice : 1 deployment

44. fast and often

45. communication

46. 2 types

47. public comms

48. REST

49. service-to-service
comms

50. REST?

51. messaging?

52. other?

53. pick

54. apply it consistently

55. Your Application
Products
Inventory
Customer
Management
Sales
Shipping
Employees
Procurement
Marketing
Invoicing
HTTP/REST
Communication Backplane

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

57. Q&A