BT

New Early adopter or innovator? InfoQ has been working on some new features for you. Learn more

From Monolith to Microservices, Zalando's Journey

| by Alex Giamas on Feb 11, 2016. Estimated reading time: 1 minute |

Last week Microxchg 2016, one of the leading conferences about microservices was held in Berlin, Germany. Rodrigue Schaefer from Zalando, a leading fashion technology company in Europe with over 10,000 employees, 1000 of them in technology, gave a speech about their transition from a monolithic application to microservices.

Using Java, Spring and Postgres stack in their monolithic application was causing a bloated codebase with many dependencies, coordination problems and eventually slower development cycles. Bug density was increasing as the team size grew and adding rigid processes to consolidate it meant that innovation suffered. Also, an “old” tech stack meant that hiring was getting slower and more difficult.

Giving trust instead of control to different teams, means that each and every team gets to pick their own technology stack and tools, taking into account their skills and the availability to get help from other departments. After nine months into the microservices transition, using AWS for provisioning, Docker for deployment and Appdynamics and Zmon for monitoring, 90% of the migration has been already done.

The mindset in such a large company around microservices dictates that with 200 microservices, one has to expect that all of them may fail at one time or another. Developers get end to end responsibility from devops to QA to deployment. Each team must act as a SaaS to the other teams, delivering a service, even if it is purely internal. And API first means that all 70 different teams must align on API rules.  These are all consolidated by a master document around rules of play, thorough peer review and a shared concept of business entities.

On the compliance and security aspect, Zalando uses the four eyes principle and extensive usage of audit trails to make sure that every change can be traced back to the individual that made it.

By banning shared libraries across different microservices, all teams are forced to open source and play by the company established rules. Finally, testing services across teams is done by a cross functional business assurance unit.

The presentation video is available on Youtube.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and dont miss out on content that matters to you

BT