ShoalStack is now
ShoalStack is now
In platform201, containers, functions, databases, queues, and schedulers share one visual graph, and each connection gives a service the values and routes it needs.
Each connection between two of your services does part of the setup work. Databases, queues,
and gateways give their values and routes to the services that use them.
Connect Cloud SQL, NeonDB, MongoDB, or a queue to a container. Its connection string arrives under the variable name that your code reads.
Put a gateway in front of all the containers and functions in your environment, and give each one its own URL path under a single HTTPS domain.
Add shared variables to the environment once. Nodes that need them refer to them by name, next to the values that their connections inject.
Connect a scheduler to a container on one of its paths.
Set its cron expression, HTTP method, timezone, and
payload, or pause it.
Request handlers, background workers, and scheduled jobs do different work. Give each one its own node with its own settings, and connect the nodes where they share data.
Send slow tasks through a queue to a worker. The API keeps responding while the work completes.
Call a processing service on a set cron schedule, and then write its results to a connected database.
Run Node.js, Go, and Python services side by side, each on its own path under the same domain.
Picture an order system in one platform201 environment: an API, a background worker, a queue,
a database, and a scheduled task. The steps show how they connect and get their settings.
In the graph editor, add a gateway, an API container, a worker, a queue, a database, and a scheduler. Set the language and port for each service.
Route /api to the API container. Connect the queue to the worker. Then connect the database to each service that reads from or writes to it.
Point the scheduler at a task path on the worker. Set its cron expression, method, and timezone. Then add any shared variables your code expects.
Deploy the environment and follow each status. The API answers at the HTTPS address of the gateway, and the worker receives its queue settings.
Start from a prebuilt graph when a known pattern fits. Its services, routes, and connections are already in place. When the result suits your team, copy it or share it.
Copy a working environment for staging or testing without rebuilding its nodes and connections.
On the Pro plan, invite team members, so they can open the graph and work on its services with you.
Start with a container behind a gateway, or begin from a Blueprint with several services in place. Add workers, queues, and schedulers when your application needs them.
Pass credentials to each service at runtime as environment variables, and keep them out of the source code and the container image. Each service then reads one variable, such as a connection string, and you can change the value without a rebuild. In platform201, a connection between a database and a service passes the value to the variable name that your code reads. platform201 stores environment variables encrypted, and it never builds them into the container image.
