Working according to a standard... really? Come on – software developers know how to build APIs. Besides, they want to stay flexible and have neither the desire nor the time to plough their way through some endless set of rules. And even if you've read them, that doesn't mean you agree with them. Fair enough. Nevertheless, there are a few challenges to overcome in software development, especially when working in autonomous teams and when you're dealing with business growth.
This post offers an insight into how we at OTTO came up with our own API Guidelines and implemented them successfully.
When we launched our platform implementation back in 2018, we jointly committed to creating state-of-the-art software aligned with thoroughly modern and proven practices. First off, we deep-dived on modern software architectures including Event Driven, Microservices, Distributed Systems, Cloud Native and DevOps – which resulted in a couple of positive architecture decisions.
My last blog article "Pimp my SAP ERP" was about how to give old SAP systems a front-end based on modern Web technologies. This blog article will be about how to operate these monolithic SAP systems ourselves in a modern and agile way using the resources of the Google Cloud Platform.
Over the past few years, microservices have grown into an established architectural approach. They are now so well established and tested that the hype is over, and enough experience is available on the benefits, limits, advantages and disadvantages. This article highlights the advantages or promises of microservice approaches that can be fulfilled when frontends are also considered.
Only too often generating and copying keys around is the way to go to talk to APIs for example from inside a container. This technique has many disadvantages from a security standpoint. The situation becomes especially crucial when privileged keys are involved, for example when used inside of CI/CD pipelines to roll out infrastructure as code. In this article our secret-less-identity-management system is introduce, an alternative approach to how we provide an identity to our CI/CD pipelines without sharing secrets but based on their context.
OTTO's history of using data centers is long and full of anecdotes. When I myself joined OTTO in 2009, most cloud providers were still in their fledgling state and cloud computing was far from being state-of-the-art for running heavy workloads.
OTTO and four 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, device 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, TikTok Information Technologies UK Limited
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. You can also withdraw your consent at any time without giving any reason by clicking on the button
'Cookie Settings' in the footer of the website and 'Refuse Cookies'.