David Leitner

Rethinking Reactive Architectures with GraphQL

How can an app stay 93% online even when the backend fails? Discover the power of reactive architectures and GraphQL subscriptions.

Rethinking Reactive Architectures with GraphQL
#1about 4 minutes

Defining reactivity and asynchronous data streams

Reactivity is defined as programming with asynchronous data streams, which are data containers that exist in plural space and asynchronous time.

#2about 8 minutes

Exploring the core principles of reactive programming

Reactive programming makes the relationship between variables explicit using streams, shifting from a pull-based design to a push-based design for automatic updates.

#3about 8 minutes

Applying reactive principles to system architecture

The Reactive Manifesto guides building responsive systems by achieving elasticity and resilience through a message-driven architecture that supports back pressure and location transparency.

#4about 7 minutes

Tracing the evolution of microservices toward reactivity

Microservice architectures evolved from synchronous pull-based models to fully asynchronous, stream-centric systems using event sourcing and functions-as-a-service.

#5about 2 minutes

Using GraphQL subscriptions for end-to-end streaming

GraphQL subscriptions provide the missing piece for end-to-end reactivity by enabling push-based data streaming from the server to the client.

#6about 4 minutes

Building a collaborative real-time insurance portal

A reactive architecture enables real-time synchronization between an insurance agent's and a customer's UI, allowing for seamless collaboration.

#7about 4 minutes

Achieving resilience in mobile banking with projections

Projections, or specialized read models hydrated from an event store, allow read-heavy features like viewing balances to remain available even when backend services fail.

#8about 1 minute

Weighing the benefits and complexity of reactive systems

While reactive architectures offer powerful options like resilience and real-time capabilities, they introduce significant complexity and should be adopted judiciously.

Related jobs
Jobs that call for the skills explored in this talk.

job ad

Saby Company
Delebio, Italy

Intermediate

test

Milly
Vienna, Austria

Intermediate

Featured Partners

Related Articles

View all articles
CH
Chris Heilmann
WeAreDevelopers LIVE days are changing - get ready to take part
Starting with this week's Web Dev Day edition of WeAreDevelopers LIVE Days, we changed the the way we run these online conferences. The main differences are:Shorter talks (half an hour tops)More interaction in Q&AA tips and tricks "Did you know" sect...
WeAreDevelopers LIVE days are changing - get ready to take part
BB
Benedikt Bischof
Why You Shouldn’t Build a Microservice Architecture
Welcome to this issue of the WeAreDevelopers Live Talk series. This article recaps an interesting talk by Michael Eisenbart who talks about the pros and cons of microservice architecture.‍About the speaker:‍Michael has been working for Bosch as a sof...
Why You Shouldn’t Build a Microservice Architecture
CH
Chris Heilmann
Dev Digest 134 - Where pixels sing?
News and ArticlesWeAreDevelopers LIVE Data and Security Day is on Wednesday, 25/09/2024. Learn about OPC UA Updates, Best Practices for Using GitHub Secrets, Passwordless Web 1.5, Emerging AI Security Risks, Data Privacy in LLMs and get a chance to t...
Dev Digest 134 - Where pixels sing?

From learning to earning

Jobs that call for the skills explored in this talk.