The database module is the core of Space Cloud. It provides instant realtime APIs on any database out there without having to write backend code. These APIs can be consumed in a secure manner directly from the frontend or from any other microservices your write at the backend. The APIs provided by this module are consistent across all the databases, simplifying database access. Thus, it acts as an unified data access layer making it easier to develop apps.
- Basic CRUD operations (create, read, update and delete)
- Get notified of the changes to your data in realtime
- Slice and dice the data being read as per your needs (i.e. filtering, sorting, skipping, limiting)
- Batch multiple mutations in a single db operation
- Transactions (Coming soon)
- Joins (Coming soon)
- Mongo DB
- MySQL and MySQL compatible databases (TiDB)
- Postgres and Postgres compatible databases (CockroachDB, YugabyteDB)
How it works
The client sends a JSON request (loosely following the MongoDB DSL) to Space Cloud describing the CRUD operation(s) to be performed. The API controller in Space Cloud first validates the request via the security module. If the request is validated, then the CRUD controller converts the JSON query to the native DB query. This native db query is then provided to the respective db driver for execution on behalf of the client. The response from the db is sent back to the client.
If any clients had subscribed to realtime changes in database, then the realtime module propagates the database changes to the concerned clients in realtime. The realtime module makes sure that whenever there is any change in the result set (results get added, removed or updated), the client will be updated. The realtime module uses a pub-sub broker under the hood to make sure the realtime piece works in a distributed fashion.
Note: Space Cloud runs a Nats server by default in the same process so that you don't have to run a broker. However, you can run your own broker and configure Space Cloud to use that instead. As of now, only Nats is supported as a broker with RabbitMQ and Kafka coming in future.
There are a few limitations in the queries which can be used while using the realtime module.
- The primary key must be _id in case of MongoDB and id for MySQL and Postgres and of type text, varchar or string.
- All documents to be inserted must have the _id (for MongoDB) or id (for MySQL and Postgres) fields set.
- The fields used in the where clause of liveQuery should not be updated by another request.
- All updates and deletes can be made on a single document only using the _id or id field in the where clause.
Note: This limitations are only applicable if you intend to use the realtime functionality.
Configure the database module
The config pertaining to crud module can be found inside the
crud key under the
modules object. Here's the snippet:
modules: crud: mongo: conn: mongodb://localhost:27017 collections: todos: isRealtimeEnabled: false rules: create: rule: allow read: rule: allow update: rule: allow delete: rule: allow realtime: enabled: true broker: nats conn: nats://localhost:4222 # Config for other modules go here
The above snippet instructs
space-cloud to connect to MongoDB at
mongodb://localhost:27017. All operations (create, read, update and delete) are allowed on the
todos collection. The realtime module is enabled and uses
nats as a broker present at
You can learn more about the various parameters available for configuring the database module here.
Now you know the basics of the database module. The next step would be diving deeper into the configuration and its structure. You could also continue to see how to use the database module on the frontend.