API
Each running Corrosion agent hosts a RESTful HTTP API for interacting with the cluster's synchronized database. Endpoints accept SQL statements in a JSON body, for versatility.
Each request is run in a transaction (as if the transaction query param had been passed).
Endpoints:
- POST /v1/transactions for writes
- POST /v1/queries for reads
- POST /v1/subscriptions to receive streaming updates for a desired query
- POST /v1/updates/{table} to receive primary-key update/delete events for a particular table