Microservices - Vancouver BC - 2018-09-20

Microservices
Sean Sullivan
Vancouver Microservices Meetup
Vancouver BC
September 20, 2018
#hbctech #gilttech #ecommerce #microservices #apibuilder #vantech

Transcript

1. Sean Sullivan September 20, 2018 Vancouver BC Microservices
2. software engineer Portland Oregon back office systems Hudson’s Bay Company About me
3. Monoliths Microservices
4. saksfifthavenue.com saksoff5th.com lordandtaylor.com thebay.com
5. saksfifthavenue.com
6. January 2016
7. June 2018
8. 2009 large monolith 2010 a few services 2011 microservices gilt.com
9. Ruby on Rails Postgres Gilt monolith (2009)
10. Gilt monolith (2009) • customer facing UI • customer service UI • purchase order management • shopping cart logic • checkout logic • order processing logic • fraud scanning • sales management • inventory management • email • return logic • daily reports
11. Gilt monolith (2009) drawbacks • unintended coupling of feature releases • single repo for customer-facing UI and non- customer-facing UI • rollbacks are more painful
12. Gilt monolith (2009) drawbacks • central coordination of each release • difficult to scale to higher levels of traffic • difficult to upgrade to new version of Ruby on Rails
13. Gilt services (2011) product service inventory reservation service shopping cart service user service checkout service credit card service kvstore service discount service order history service
14. 2012 L.O.S.A. 2013 binary coupling hell 2014 ApiBuilder gilt.com
15. L.O.S.A. ?
16. Lots Of Small Applications
17. Customer facing UI was a monolithic app (hundreds of JSP’s in a single Git repo)
18. large UI monolith smaller UI apps
19. Gilt L.O.S.A. web- product- detail web- homepage web-mosaic web-search web- account web- checkout web-login web- navigation web-seo- page
20. Lots Of Small Bugs Lots Of Small Applications
21. Benefits of L.O.S.A. • easier to troubleshoot UI bugs • easier to implement bug fixes • easier to test the fix • easier to release fix to production
22. binary coupling gilt.com (2013)
23. binary coupling can emerge in large microservice systems
24. binary coupling was a significant problem at Gilt.com and Netflix
26. how to mitigate binary coupling?
27. API descriptors + code generation
28. ApiBuilder gilt.com (2014)
29. describe REST API in a JSON file
30. www.apibuilder.io
32. code generation
33. Web Checkout Android Checkout iPhone Checkout Checkout service
34. ApiBuilder CLI
35. $ brew install apibuilder-cli $ cd myproj $ vi .apibuilder/config $ apibuilder update
36. 2015 migrate to AWS 2016 AWS cloud native gilt.com
37. 2017 embrace serverless 2018 payment platform v3 2018 shutdown gilt.com
38. lessons learned from gilt.com
39. decentralized decision making
40. minimize undifferentiated heavy lifting
41. one path to production
42. small, autonomous teams
43. end-to-end ownership
44. deploy to production everyday
45. small incremental releases
46. ApiBuilder is awesome
47. developer experience matters
48. continuous improvement
49. testing in production
50. feature flags
51. engineering velocity is a competitive advantage
53. HBC 2018 • multi-tenant services • ApiBuilder • safe deployments
54. Mark Zuckerberg
55. Move Fast and Break Things Move Slow and Don’t Break Things
56. https://twitter.com/jaykreps/status/312338174108106754
57. Move Fast and Don’t Break Things Move Purposefully and Fix Things
58. continuous delivery
59. https://twitter.com/evanderkoogh/status/1036787227697664000
60. Email @ HBC
61. HBC email types • order acknowledgement • order shipment partial • order shipment full • order cancel • ready for pickup in store
62. Queue consumer Event queue Email Dashboard UI Email Sender Email Render External Email Provider Feature Flag service
63. Email Render Product Detail service Delivery Date Estimation service request HTML Feature Flag service
64. HBC email system • multi-tenant design • Cloudwatch Metrics • Cloudwatch Alerts
65. HBC email system • code coverage threshold • components deployed independently • safe deployments
66. safe AWS Lambda deployments?
67. traffic shifting
68. You can now shift incoming traffic between two AWS Lambda function versions based on pre-assigned weights. You can now also use AWS CodeDeploy to automatically manage the rollout of new function versions. This allows you to gradually shift traffic between two versions source: aws.amazon.com
69. AWS traffic hooks • PreTraffic hook • PostTraffic hook
70. Final thoughts autonomous teams ApiBuilder engineering velocity is a competitive advantage
71. https://www.infoq.com/presentations/microservices-arch-infrastructure-cd
72. The end