Gregor Hohpe

Share

Chief IT Architect at Allianz, co-author of “Enterprise Integration Patterns”

 www.enterpriseintegrationpatterns.com
 @ghohpe


Gregor is a recognized thought leader on asynchronous messaging and service-oriented architectures. He is widely known as co-author of the seminal book “Enterprise Integration Patterns” and as frequent speaker at conferences around the world. He is an active member of the IEEE Software editorial advisory board.

As Chief IT Architect at Allianz, Gregor is responsible for driving the digital transformation of the insurance business. He documented his experience as an architect driving IT transformation in the eBook ””37 Things One Architect Knows”“.

Books

Enterprise Integration Patterns: Designing, Building, and Deploying Messaging Solutions

37 Things One Architect Knows About IT Transformation: A Chief Architect’s Journey

Enterprise Solution Patterns Using Microsoft .NET

Integration Patterns (Patterns & Practices)

The Best Software Writing I

97 Things Every Software Architect Should Know: Collective Wisdom from the Experts

97 Things Every Programmer Should Know: Collective Wisdom from the Experts

Recent Articles

Gregor’s Ramblings on Enterprise Integration

Messaging Patterns

Recent Interviews

A Decade of Enterprise Integration Patterns: A Conversation with the Authors

YOW! 2016 Melbourne

If You Are Synchronous You Are Not Resilient

TALK – VIEW SLIDES
Your software will break. The more sophisticated it is, the more often it will break. While traditional software design tries to eliminate failure through extensive testing, modeling and other techniques, highly scalable and dynamic systems need to embrace failure. Instead of trying to be robust, these systems need to be resilient, e.g. by restricting the extent of failure through isolated failure domains. Synchronous, state-sharing approaches like many object-oriented systems are notorious for propagating failure and make it difficult to isolate failure. Decoupled, asynchronous systems can add resilience.

This session takes a journey through coupling, asynchrony, conversations, and patterns for resilient software design.

KEYWORDS

Messaging, Architecture, Resilience, Scaling, Asynchrony, Patterns, Design, Decouping