With the introduction of the Revolt event loop in Drupal Core, we're getting ready for Drupal to tackle an entirely new class of problems: asynchronous applications. In this session you'll find out how to think asynchronously and leverage Revolt in your applications.

Prerequisite
An intermediate understanding of PHP and Drupal is encouraged to understand the examples, but we'll build your asynchronous understanding from scratch.

Outline
We'll start with a short recap of how synchronous/blocking applications work and why asynchronous applications can provide us with new opportunities.

Then we'll take a look at the status of Drupal core's adoption of Revolt and turning it asynchronous.

With that in mind we'll look at the task coordination problems that arise when moving to asynchronous code and how the event loop can help us solve them. From there we'll dive deeper into how futures can help us be decisive about our branching logic and coordinate successes and failures

Finally we'll take a look at the amphp set of libraries, which are not in Drupal core, but can be used in your own projects and contrib modules to apply the things you've learned without having to think about the nitty gritty.

Learning Objectives
After this session you'll know:

1. Where Drupal Core is at in its adoption of Revolt
2. How to think about your application with an asynchronous mindset
3. How Future's work
4. What problems the amphp libraries have already solved and the tools you can add to your toolbox

Experience level
Intermediate