This document discusses planning for scaling software systems. It recommends dividing the system into independent services that communicate via APIs. It also stresses the importance of establishing shared infrastructure for components like packaging, deployment, monitoring and identity management. Teams should be empowered and trusted to own their services but interact through well-defined and documented APIs.

1. Brendan Burns
Software Engineer, Microsoft Azure
Co-founder Kubernetes

22. But…

28. What pieces do we need?

29. Planning to Scale
Container
Web Server
Database

30. Planning to Scale
Container
Web Server
Database
Container
Web Server
Database

31. Container
Planning to Scale
Container
Web Server
Database

32. Container
Planning to Scale
Container
Web Server
Database
Container
Web Server
Container
Web Server

33. Container
Planning to Scale
Container
Web Server
Database
Container
Web Server
Container
Web Server

34. Planning to Scale Teams

35. Products are UX on top
of APIs

37. Define boundaries

38. Decouple
This Photo by Unknown Author is licensed under CC BY

39. Empower

40. But…

41. Ground Rules for APIs

42. Deprecation Policy

43. Documentation

44. Quality of Service

45. Teams interact via APIs

46. Don’t ask, Don’t tell

47. Trust No One

48. No backdoors
(dogfood your apis)

49. But…

53. You must establish core
infrastructure

54. Language(s)

55. Packaging &
Deployment

56. Continuous Testing and
Delivery

57. Monitoring
Logging
& Alerts

58. API & RPC
Infrastructure

59. Identity
Authorization
& Secrets

60. Storage

61. Analytics
& Experiments

62. Summing Up

63. Scale your team not your service

64. Think in APIs

65. Empower Individuals
(& individual teams)

66. Build on shared infrastructure

67. Thank you!