Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2wgtbXC. Andrew Hart talks about the architectural, operational, and cultural aspects of evolving a microservice architecture, in the process highlighting both the opportunities and the challenges that microservice architectures present. Filmed at qconnewyork.com. Andrew Hart is the Platform Director for SeatGeek Open, SeatGeek’s primary ticketing solution. A member of the Apache Software Foundation, he was previously CTO of Pogoseat and a software Engineer at NASA. He has had work published in a variety of academic journals and has a long-standing passion for connecting people with data in meaningful ways to enable better decision making.

1. Take 2: Evolving
Microservice Architectures
Andrew Hart – Platform Director, SeatGeek Open

2. InfoQ.com: News & Community Site
• 750,000 unique visitors/month
• Published in 4 languages (English, Chinese, Japanese and Brazilian
Portuguese)
• Post content from our QCon conferences
• News 15-20 / week
• Articles 3-4 / week
• Presentations (videos) 12-15 / week
• Interviews 2-3 / week
• Books 1 / month
Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
evolving-microservices-architecture

3. Presented at QCon New York
www.qconnewyork.com
Purpose of QCon
- to empower software development by facilitating the spread of
knowledge and innovation
Strategy
- practitioner-driven conference designed for YOU: influencers of
change and innovation in your teams
- speakers and topics driving the evolution and innovation
- connecting and catalyzing the influencers and innovators
Highlights
- attended by more than 12,000 delegates since 2007
- held in 9 cities worldwide

12. Microservices made this POSSIBLE.

13. Who has a
MICROSERVICE ARCHITECTURE?

14. Who WANTS TO HAVE a
microservice architecture?

15. “You probably already have a
microservice architecture
whether you want one or not”

16. CHANGE

17. Technology

18. Technology, scale

19. Technology, scale, organization

20. How can a microservice architecture HELP?

21. EVOLUTIONARY architecture

22. organized around CAPABILITIES

23. MORE than (just) architecture

24. Architecture, DEVOPS

25. Architecture, devops, CULTURE

26. Architecture

27. Atomic COMPONENTS

28. HARD to get this right

29. Here is an event ticket

30. It's this one…
"FC4"

31. What section is this?
"F4ADA"

32. It's this one…
"FC4"

33. NORMALIZATION

34. F4ADA Field Club S4 FC04
FC4

35. DIAGRAM 1: normalization

36. DIAGRAM 1: normalization

37. DIAGRAM 1: normalization

38. DUPLICATE the functionality?

39. Duplicate the capability?
PROMOTE the capability to a component?

40. Duplicate the capability?
Promote the capability to a component?
RE-IMPLEMENT the interface?

41. DIAGRAM 3: normalization

42. avoid DUPLICATING CAPABILITIES
between components

43. Assumptions WILL CHANGE over time

44. Think about CAPABILITIES

45. Consider the RELATIVE COST

46. SCALE

47. Architecture
⇏
"IT WILL JUST WORK"

48. DIAGRAM 4: SRO Integration

49. SeatGeek RAISES $57M to acquire ticketing software
company TopTix

50. DIAGRAM 5: SRO Integration (2)

52. ALL THE SEATS

53. 30-50MB XML (SOAP) messages
+
Dynamically Typed Python Libraries
=

54. SeatGeek's first steps with

56. ENCAPSULATE the SOAP

57. Encapsulate the SOAP,
INTERPRET the messages

58. Encapsulate the SOAP,
Interpret the messages,
Present a STANDARD INTERFACE

60. DIAGRAM 6: SRO Integration (4)

61. Capacity planning is IMPORTANT

62. Devops

63. Microservice architecture <3 PAAS

64. SeatGeek operates an Internal PAAS

69. INDEPENDENT
deployments
MINIMAL
coordination
NO
machine-local state

70. How do you deal with change and uncertainty?

71. How do you deal with change and uncertainty?

72. PAAS infrastructure simplifies
EVOLVING a microservice architecture

73. MONITORING

75. DIAGRAM 7: Tick Stack SG Implementation

76. Atomic components

77. Atomic components

78. Atomic components

79. Ubiquitous service monitoring can help
identify operational risks

80. Culture

81. ALIGNMENT

82. "organizations which design systems ... are
constrained to produce designs which are
copies of the communication structures of
these organizations"
Melvin Conway, 1968

83. SeatGeek MISSED a few internal deadlines

84. Team structure
DID NOT REFLECT (desired) CAPABILITIES

85. DIAGRAM 8: SG Org (1)

86. DIAGRAM 8: SG Org (2)

87. DIAGRAM 8: SG Org (3)

88. DIAGRAM 8: SG Org (4)

89. Evolving an architecture might require
re-evaluating
ORGANIZATIONAL RESPONSIBILITIES

90. DOCUMENTATION

91. KNOWLEDGE lives with teams

92. Teams CHANGE over time

93. Documentation needs to be
"HIGHLY AVAILABLE"

94. Back to March 11, 2017…

100. finis

101. Andrew Hart
Platform Director, SeatGeek Open
hart@seatgeek.com
Twitter: @andrewfhart
Web: http://www.andrewfhart.com/
SeatGeek Open is looking for engineers!
https://seatgeek.com/jobs/software_engineer_sg_open

102. This slide intentionally
left blank.

103. Watch the video with slide
synchronization on InfoQ.com!
https://www.infoq.com/presentations/
evolving-microservices-architecture