Terraforming your AWS Cosmos
In einer immer komplexer werdenden Infrastrukturlandschaft trifft man häufig auf eine legacy Infrastructure.
Aber warum? Meist hat irgend jemand vor langer Zeit die Landschaft aufgesetzt, der heute nicht mehr im Projekt ist. Wartung hat nie stattgefunden und eine Dokumentation gibt es natürlich auch nicht.
Was tun? Infrastructure as Code kann diese Probleme lösen, denn es schafft mehr Dokumentation, Revisionssicherheit und reduziert die Komplexibilität.
Let the monoliths collapse
Henning Teek (Storm Reply) was talking about monoliths and how to avoid pitfalls while migrating to microservices at our AWS User Group event in August 2019.
Read moreAWS ML Stack
The 6th of August Fabian Zhindon Astudillo presented at the AWS User Group Dortmund about the Machine Learning Stack of the platform.
Read moreAWS Fargate: Containerization meets Serverless
In July we had Vadym Kazulkin and Benjamin Jung as guest in the AWS User Group Dortmund again in the Storm Reply offices.
Read moreChaos Engineering – withstanding turbulent conditions in production
In June Benjamin Wilms from codecentric presented in our User Group about why we need Chaos Engineering.
Read moreAmazon Document DB Slides
As a re:cap to our Meetup from the 15th of March with Joseph Idziorek we like to present additional content for you.
Read morere:invent re:cap with Frank Munz
On the 10th of December Frank Munz (@frankmunz) gave an interesting re:cap to the 2018 AWS re:invent, with more than 100 annoncements.
Read moreNew AWS UG homepage online
We just set up a new homepage for the AWS UG. You will find recaps about bygone Meetups here and in addition we will try to generate cloud related content.