It is possible to add extra local data storage services in the Local Simple Runtime. A containerized test environment is great for testing and can be deleted at any time. These services can also be accessed directly via 127.0.0.1 instead of host.docker.internal.
Triggers - API route, MQ and scheduler - CLI commands.
CLI allows you to create data process projects locally and deploy them with console commands.
API routes is one of the trigger features that can be deployed and managed from CLI, which make data processes RESTful-like. See Triggers commands for more details.
Message queue clients, publishers and subscribers together are one of the trigger features that can be deployed and managed from CLI.
Scheduler - schedules and scheduled jobs - together are one of the trigger features that can be deployed and managed from CLI. See Triggers commands for more details.
LOC data events allows users to generate a data flow or data trail to indicate who have sent and received data. These information can be very useful for two reasons:
This is the follow-up of Emit and Inspect Events, in which we've learned the basics of emitting events.
General, profile and login CLI commands.
Logic are the core elements of a data process. They contains the implementation of part of a data pipeline. And the session storage is the thing to link them up together.
Project, data process and logic CLI commands.
LOC CLI is the command line tool for developers to deploy data processes and manage other assets in LOC.
If a data process is deployed, it can be run without using triggers. This is exactly the same as the Execution function in Studio.
Tag and unit CLI commands.
Some tips about handling errors in logic.
Local Simple Runtime is a Docker-based local LOC environment. It offers the following benefits: