Dirk Fröhner

In this code talk, you'll instrument an event-driven integration layer with the patterns that contain failure: exponential backoff with jitter, circuit breakers, poison-pill isolation, and replay-from-archive - all live, in code.

Design patterns are powerful tools for software architects. When modernizing legacy applications, three patterns hold special significance: Strangler Fig, Circuit Breaker, and Sagas.

Today's applications are interconnected: they expose APIs, publish events, call third-party services, and externalize states. They must therefore address the fundamental challenges of distributed systems, such as out-of-order delivery, retries, idempotence, and partial failures.

Today's SaaS applications are interconnected: they expose APIs, publish events, call third-party services, and externalize states. Adding multi-tenancy to these integrations introduces new challenges.

Today’s applications are interconnected: they expose APIs, publish events, call third-party services, and externalize states. They must therefore address the fundamental challenges of distributed systems, such as out-of-order delivery, retries, idempotence, or partial failures.

This chalk talk explores advanced strategies for managing multi-tenant Amazon SQS queues, discusses the challenges posed by noisy neighbors, and shares effective mitigation techniques, including shuffle sharding and overflow queues.

In this chalk talk, explore the power of dead-letter queues (DLQs) for managing unconsumed messages in decoupled applications. DLQs provide a mechanism for handling messages that cannot be processed successfully.

Amazon SNS, Amazon SQS, and Amazon EventBridge are robust, scalable services that are fundamental building blocks for distributed architectures. In this chalk talk, explore how to combine these services to effectively tackle common challenges, including ordering, only-once processing, and throttling.

Virtually all integration approaches come with trade-offs. However, loosely coupled integration can help you design independent systems that can be developed and operated individually and can also increase the availability and reliability of the overall system landscape—particularly by using asynchronous communication.

Companies may deal with integration challenges in many areas and on many layers, and all integration approaches come with their individual trade-offs. However, loosely coupled integration can not only help with designing independent systems that can be developed and operated individually but can also increase availability and reliability of the overall systems landscape.

Sometimes architects are unsure about which application integration approach is best for their use case. There are many integration options, from file transfer over HTTP-based APIs to messaging and streaming.

An implication of applying the microservices architectural style is that a lot of communication between components is done over the network. In order to achieve the full capabilities of microservices, this communication needs to happen in a loosely coupled manner.

Sometimes, architects are unsure about which application integration approach is best for their use case or access pattern. Aside from APIs, options to choose from include messaging, streaming, and events.

One of the implications of applying the microservices architectural style is that a lot of communication between components is done over the network. To achieve the promises of microservices, this communication needs to happen in a loosely coupled manner.

You don't need to be a data scientist to build an AI application. In this workshop, we show you how to use AWS AI services to build a serverless application that you can use to understand your customer interactions.

Often, when the microservices architecture style is applied, much of the communication between components is done over the network. In order to achieve the promises of microservices, this communication needs to happen in a loosely coupled manner.

One of the implications of applying the microservices architectural style is that a lot of communication between components is done over the network. In order to achieve the promises of microservices, this communication needs to happen in a loosely coupled manner.

Utilities are reinventing themselves as digital businesses to deliver new products and services and frictionless customer experiences. How effectively you manage your data as a strategic asset is quickly becoming a competitive differentiator, especially in deregulated markets.