The Rise of Modern Transactional Stack
AI Generated Video Summary
1. Architectural Shifts in Transactions
2. Modern Transactional Stack and Workflow Engines
I used to provision infrastructure all the time and it's not fun. In this architecture, you will also utilize services that can scale down to 0 and scale up based on demand quickly. Removing the need for DevOps teams altogether. Another trait of the modern transactional stack is that it's powered by component-driven toolings. For authentication, you no longer need to deal with lower-level tools backend engineers traditionally use. Now you can just pick up tools like Clerc and use a signing React component. For object storage, you can use something called UploadThing natively in React instead of using AWS S3 directly. Lastly, as businesses use more APIs and accept more webhooks, they have to deal with async functions at scale. Workflow engines play a central role in the serverless native world, orchestrating async functions. If you want to chat more, feel free to send me a DM on Twitter at staff Yoko Draws. Thank you.
I used to provision infrastructure all the time and it's not fun. In this architecture, you will also utilize services that can scale down to 0 and scale up based on demand quickly. Removing the need for DevOps teams altogether. Upsash is a great example of this.
Second, another trait of the modern transactional stack is that it's powered by component-driven toolings. For authentication, you no longer need to deal with lower-level tools backend engineers traditionally use. Now you can just pick up tools like Clerc and use a signing React component. Another good example here is an open-source project called React Email. You no longer have to code vanilla HTML for transactional emails and now you can just use React and Tailwind directly in your email. For object storage, this is always something that a lot of engineers tell me and even myself, how to learn AWS for. But now you can use something called UploadThing natively in React instead of using AWS S3 directly.
Lastly, one highlight of this stack is that as businesses use more APIs, more functions and accept more webhooks, they essentially have to deal with async functions at scale. So when this happens, there needs to be a central place to orchestrate these things since handcrafted retries are hard. Now we start to see workflow engines playing a central role in the serverless native world. And the way to understand them is that they are the orchestrator of async functions. Here's the intuition. If your app handles hundreds of user signups and then sends a bunch of welcome emails to the users, you can use tools like ingest to write a few lines of TypeScript code to define what functions should be triggered when a signup event happens. It will also retry this part of the logic automatically with exponential backoff if that process fails. And on the client side, if you want, you can use the authoring layer of the state machine called xState. I hook it up with the workflow engine. It's a super cool project, makes things much easier to reason about compared to Redux which I used to use all the time.
There is probably hours and days of things to talk about in a stack we see over and over again here in the serverless era. If you want to chat more, feel free to send me a DM on Twitter at staff Yoko Draws. And that's all I have today. Thank you.