Multi-service architectures: running an app as several services
How to split an application into a web service, a background worker and a database, why teams do it, and how each piece is created on Voroa right now.
What this covers
Most applications start as one process and eventually want to be three. The web service answers requests and must stay fast. Slow work, such as generating a report or sending a batch of email, moves to a background worker so it cannot block a request. State moves to a managed database so that restarting either process loses nothing. The pieces talk to each other over the network, using connection details you pass in as environment variables rather than hardcoding.
A guide on planning and connecting a multi-service application is not published in the Voroa docs today. Each individual piece can be created now, and connected by hand using environment variables.