PliantDb aims to offer the majority of its functionality in local operation. The networked server adds some functionality on top of the local version, but its main function is to add the ability to use networking to talk to the database.
Because of this model, it makes it easy to transition a local database to a networked database server. Start with whatever model fits your needs today, and when your neeeds change,
PliantDb will adapt.
- You're going to databases from one process at a time.
PliantDbis designed for concurrency and can scale with the capabilities of the hardware. However, the underlying storage layer that
PliantDbis built upon, sled, does not support multiple processes writing its data simultaneously. If you need to access the database from multiple processes, the server integration is what you should use. While it doesn't offer IPC communication today, a pull-request would be accepted to that added that functionality (along with the corresponding unit tests).
- You have no public API/PubSub/access needs or have implemented those with another stack.
- You need to access databases from more than one process or machine.
- You are OK with downtime due to loss of service when the single server is offline. If you need to have a highly-available database, you should use the Cluster Integration (Coming Soon).
- Your database load can be met with a single machine. If you have enough load that you need to share the processing power of multiple servers, you should use the Cluster Integration (Coming Soon)
- You need to access databases from more than one machine.
- You need a highly-available setup.
- You need/want to split load between multiple machines.