Developers Roadtrip to Heaven? myToys transition from SOA to Microservices Architecture
1. Developers Roadtrip to Heaven? myToys transition
from SOA to Microservices Architecture
About The Presenters
Dr. David Lee
BSc(Hons) Computing for Business and E-Commerce / PhD in Computer
Science (Robert Gordon University, Aberdeen, Scotland)
Certified Software Architect (Foundation Level)
2010-2014: Backend Software Developer at myToys.de
2014-Present: Software Architect at myToys.de
Dipl. Inf., Dipl. Vw (Freie Universität Berlin)
10 Years Experience as Researcher
Experience as Senior and Lead Software Developer in various companies
2015-Present: Software Architect at myToys.de
Multishop Platform (Service Orientated Architecture)
• Aim: Develop platform so features developed once but usable for all
shops. Retain individual design of shops.
Positive Experience with Service Orientated
Business Relevant Services für every shop.
Services deployable separately.
More independent teams than with monolithic application.
Content Management System
Many change requests only affect the frontend part (HTML/CSS).
Challenges with Service Orientated Architecture
Development and release co-ordination Backend <> Frontend.
Frontend Monolithic breaks Conways‘s Law.
Separated Data Layer
Big Challenge where bugs located.
Transition to Microservices (1):
Microservice Microservice Microservice Microservice
Transition to Microservices (3):
How it works in the background
with Service URLs
Transition to Microservices (4):
Transition to Microservices (5):
Microservice Store and Live Editor
Summary of key components for TechVision
Team Split /
Independence / Self-
Elastic Load Balancing Continuous Delivery
Automatic Documentation Test Driven
PO / first Level Support
Live Shop Editor
Interactive Discussion Groups
• There are 4 groups:
• Page Assembling
• Continuous Delivery
• Cloud, Elastic Load Balancing and Service Discovery.
• Discussion Groups: after pizza until 8.30pm. Visit each group – how
long is up to you.
• Summary afterwards.
Group #1: Microservices (Timo Fleischfresser)
„The name of Microservices suggests that it affects the size of the service
– and obviously services should be small. One possible definition for the
size of a microservice is …“ [Eberhard Wolff, Microservices]
• Lines of Code
1.What are good measures for defining the size of a microservice?
2.What are bad measures for defining the size of a microservice?
Group #2: Page Assembling
1.What are the
responsibilities of a Page
2.Which tasks are
performed better by other
3.Is it possible to do
assemble a page
completely on the client
Group #3: Continuous Delivery (Andreas Lehmann)
1.How do we manage the trade-off
between speed and quality in the
continuous delivery approach?
2.For which situations may it better to be
fast rather than have the highest
3.For which situations may it better to
have higher quality than a fast pipeline?
Group #4: Cloud, Elastic Load Balancing and Service
Discovery (David Lee)
1.Let‘s use the cloud! What are the
challenges of making applications
2.What are the advantages and
disadvantages of the main cloud
providers based on your