Moderne Architekten machen erheblich mehr als UML Diagramme zeichnen oder Architekturstile zu katalogisieren. Sie liefern enormen Wert, indem sie die Unternehmensstrategie mit technischen Entscheidungen im Maschinenraum verknüpfen. Dies erfordert Fingerspitzengefühl und die Fähigkeit, komplexe technische Zusammenhänge und Abwägungen auf verschiedenen Ebene zu kommunizieren, ohne die Inhalte zu verwässern oder das Publikum zu verwirren. Dieser Talk hilft Architekten dabei, den “Architect Elevator” zwischen Maschinenraum zur Firmenleitung zu fahren.
As Director of Enterprise Strategy at AWS, Gregor helps technology leaders transform both their organization and their technology platform. You’ll find him riding the Architect Elevator from the engine room to the penthouse, perhaps automating serverless solutions in the morning and preparing board presentations in the afternoon. His favorite pastime is dissecting buzzwords and replacing them with meaningful decisions and architectural trade-offs.
Before joining AWS, Gregor has served as Smart Nation Fellow to the Singapore government, as Technical Director in Google Cloud’s Office of the CTO, and as Chief Architect at Allianz SE, where he oversaw the architecture of a global data center consolidation and deployed the first private cloud software delivery platform.
Gregor is known as co-author of the seminal book Enterprise Integration Patterns, which provided the reference vocabulary for all modern ESBs. His book The Software Architect Elevator tells stories from the trenches of IT transformation while his articles have been featured in Best Software Writing by Joel Spolsky and 97 Things Every Software Architect Should Know. He is an active member of the IEEE Software advisory board.
Ein unschlagbarer Vorteil von Konferenzen vor Ort: Die Welcome Reception! Kommen Sie wieder in gemütlicher Runde mit anderen Teilnehmenden und Speakern ins Gespräch.
Designing good applications has become more demanding than ever: Extremely flexible, very high availability, scaling up and down on demand, rising user demands, sustainability, APIs as first class citizens while being secure like a fortress at the same time, and so on. The list appears to be endless.
In the past, quite some of today's application demands have simply not existed yet. And some others we could easily delegate to the operations team. But that is not possible anymore.
In this session, we will take a look at how our application design demands have changed, what you need to take into account to design good applications and how to tackle the challenges best.
Let us get ready for the architectural work of the upcoming years and learn how to square the circle
Uwe Friedrichsen travels the IT world for many years, always in search of innovative ideas and concepts. His current focus areas are system design, resilience, sustainability and making IT a (bit) better place. Often, you can find him on conferences sharing his ideas, or as author of articles, blog posts, tweets and more.