20160512 GOTO night pragmatic micro services
•Download as PPTX, PDF•
1 like•1,305 views
GOTO Night presentation on pragmatic (micro) services: Monoliths, services and microservices @ bol.com
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
20160512 GOTO night pragmatic micro services
- 1. Monoliths, services and microservices @ bol.com Peter Paul van de Beek May 12, 2016 1
- 2. The shop for everyone 2
- 3. 3 Multi-channel approach Mobile website / Mobile weblog / Mobile marketing eBook apps External apps
- 4. Bol.com from online bookshop to portal for specialised online channels serving the entire Dutch-language region 4 Books Entertainment Electronics Toys Preloved sales eReading Small Appliances White Goods Marketing via bol.com Baby Cooking & Tableware Health & Beauty Home & BedroomPets Garden & DIY 2004-2007 2010 Sports & Leisure 1999-2003 2010 2011 2012 2013 2014 2015 Jewellery & Watches Bags & Accessories SECOND-HAND ePRODUCTS COMMERCIAL MARKETING NEW SPECIALISED CHANNELS ALSO WORTH KNOWING Startup in a portacabin Active in Belgium Takeover by Ahold 2008-2009
- 5. • Over 6 million active customers • Virtual footfall of almost 1 million per day • Over 11 million products • More then a 1.000 employees in Utrecht • 1 in 2 Dutch and Belgian customers who shop online, do so on bol.com • Ranked among top 10 businesses for customer satisfaction 5 Where is bol.com now? >95% >75% Brand awareness
- 6. 6
- 7. 7 IT has a high pace
- 8. 8 10 to 50 scrum teams in 3 years
- 9. 9 Space – Fleet – Team Retail Platform Fulfillment Network Shopping Experience Technical Platform
- 10. 10
- 11. • A few monoliths • Expose services on the monolith • Carve out functionality • Create new functionality as services • Split “older” services 11 History of services @ bol.com
- 12. • Catalogue • Web shop • Sourcing / Fulfillment What do you need as an online retailer… 12 The early ages
- 13. “The many things that you would like to see happening in a good software environment couldn’t be done anymore; there were many complex pieces of software combined into a single system. It couldn’t evolve anymore. The parts that needed to The parts that needed to scale independently were tied into sharing resources with other unknown code paths. There was no isolation and, as a result, no clear ownership.” Werner Vogels 13
- 14. • The shop stays open • Technical innovation is enabled by business value • Scalability is a business thing • The hard thing: define boundaries • One purpose • Some how stuff • Start with a good API • Use mappers where we can’t change the environment 14 Carve out services
- 16. • Choose the path of the least hurt • Decisions matter not paper 16 Architecture is always a trade off
- 17. • Rest • Or queueing (async) • Swagger • CI / CD • Mayfly 17 Technical stuff
- 18. 18 How many service are involved?
Editor's Notes
- http://www.meetup.com/GOTO-Nights-Amsterdam/events/228918132/
- We believe in the need to shape elegant and adaptive IT solutions to enable bol.com to achieve their ambitions, today and tomorrow.
- “druk” om snelheid te houden Innovatie te blijven doen
- https://en.wikipedia.org/wiki/Werner_Vogels No longer able to explain _all_ changes in one release; Changes of one team interfered with others; Ownership Speed: slows down … Where to start???