1
 
 
Account
In your account you can view the status of your application, save incomplete applications and view current news and events
wMetadata:title
October 04, 2018

OTTO goes AWS - Part 1

160+ Services, 24 Teams, 1 year

The cloud stands for scalability, cost efficiency and short time to market for new features. otto.de also wants to benefit from this and therefore started the migration to AWS last summer.

The first question was how the whole thing should be organized. Centralized or decentralized? Agile or conservative project management? We decided on everything at the same time - a largely decentralized implementation with a hybrid project management approach.

Organizationally, a central migration team was created to support our decentralized development teams. The motto here is always help for self-help by means of a mentoring conceptEach team therefore had a fixed contact person with whom architecture decisions, concrete implementation details or questions relating to the cultural change were discussed. An accompanying framework program consisting of six workshops was also established, in which central concepts, problems or call-for-support were discussed from team to team. The agenda was generally designed in an agile manner and changed several times a day as needed.

The development teams continued to work in agile mode and regularly synchronized progress with the central project plan, which was a kind of milestone plan. Risks could thus be identified at an early stage and minimized by taking appropriate measures.

Important issues during the migration were

  • Central vs. decentralized implementation of certain aspects
  • Strategy in supporting our development teams
  • Implementation of a security strategy
  • Communication between our individual services, esp. VPN or no VPN?
  • Dealing with vendor lock-in effects
  • In-house development of services vs. standardized high-level services

These and other questions will be considered in subsequent articles.

But what was the biggest challenge? It was not the technological implementation, but rather the cultural shift toward decentralized operation of the infrastructure. Previously, operational responsibility rested with a central operations unit. Now the teams are completely autonomous and have to deal with issues such as readiness or disaster recovery. So it makes sense in any case to accompany such a project with appropriate change management measures.

After this very exciting and eventful year, the foundation has now been laid for the ever-growing requirements - e.g. the platform project.

5Comments

  • […] wir bei Otto vor kurzem unsere komplette Infrastruktur in die AWS migriert haben, wollten wir erst Erfahrungen sammeln bevor wir dort Kafka in Eigenregie betreiben. Zur […]

  • 11.01.2019 15:44 Clock

    […] Welche Fragen und Herausforderungen Otto bei diesem Projekt meistern musste, könnt ihr im Otto Entwicklerblog […]

  • Dieter Kuntz
    05.10.2018 11:58 Clock

    Schöner Beitrag! Sehr interessant zu lesen, wie dieses Unternehmen einschlägige strukturelle Veränderungen zu meistern weiß. Alles Gute für die Zukunft.

  • […] – gibt’s erst in der nächsten Woche. Daher nur kurz vor dem Wochenende: In einem kurzen Artikel im Otto-Dev-Blog berichtet der Autor, wie man mit 24 Teams und mehr als 160 Services innerhalb eines Jahres zu AWS […]

  • Stephan
    09.10.2018 10:08 Clock

    Vielen Dank für de Post! Vielleicht könntet ihr in einem 2. Post noch etwas mehr Details liefern? Welche AWS Dienste wurden z.B. genutzt und welche positiven und negativen Erfahrungen habt ihr damit gesammelt? An welchen Stellen hat der Wechsel zu AWS eure Architektur wie beinflusst? Waren die Services vorher schon "Cloud-fähig" oder gab es Änderungen die dadurch notwendig wurden?

Write a comment
Answer to: Reply directly to the topic

Written by

Fabian Hoffmann

Similar Articles

We want to improve out content with your feedback.

How interesting is this blogpost?

We have received your feedback.

Allow cookies?

OTTO and three partners need your consent (click on "OK") for individual data uses in order to store and/or retrieve information on your device (IP address, user ID, browser information).
Data is used for personalized ads and content, ad and content measurement, and to gain insights about target groups and product development. More information on consent can be found here at any time. You can refuse your consent at any time by clicking on the link "refuse cookies".

Data uses

OTTO works with partners who also process data retrieved from your end device (tracking data) for their own purposes (e.g. profiling) / for the purposes of third parties. Against this background, not only the collection of tracking data, but also its further processing by these providers requires consent. The tracking data will only be collected when you click on the "OK" button in the banner on otto.de. The partners are the following companies:
Google Ireland Limited, Meta Platforms Ireland Limited, LinkedIn Ireland Unlimited Company
For more information on the data processing by these partners, please see the privacy policy at otto.de/jobs. The information can also be accessed via a link in the banner.