Difference between revisions of "Trove/DatastoreCompatibilityMatrix"
< Trove
(→API Matrix) |
(→Extensions Matrix) |
||
Line 68: | Line 68: | ||
| ✔ | | ✔ | ||
| style="color: red" | ✗ | | style="color: red" | ✗ | ||
− | | | + | | ✔ |
− | | | + | | ✔ |
| ✔ | | ✔ | ||
|- | |- | ||
Line 75: | Line 75: | ||
| ✔ | | ✔ | ||
| style="color: red" | ✗ | | style="color: red" | ✗ | ||
− | | | + | | ✔ |
− | | | + | | ✔ |
| ✔* | | ✔* | ||
|- | |- |
Revision as of 17:38, 3 February 2014
This page will detail which datastores have which functions, either core or extension form.
API Matrix
Feature | MySQL | Redis | Cassandra | MongoDB | PostgreSQL |
Launch | ✔ | ✔ | ✔ | ✔ | ✔ |
Reboot | ✔ | ✔ | ✔ | ✔ | ✔ |
Terminate | ✔ | ✔ | ✔ | ✔ | ✔ |
Resize | ✔ | ✔ | ✔ | ✔ | ✔ |
Backup | ✔ | ✔ | ✔ | ✔ | ✔ |
Restore | ✔ | ✔ | ✔ | ✔ | ✔ |
Extensions Matrix
This covers items that are not considered part of the core api (yet). As more datastores start to use extensions, we can move them to core.
Feature | MySQL | Redis | Cassandra | MongoDB | PostgreSQL |
Users | ✔ | ✗ | ✔ | ✔ | ✔ |
Schemas | ✔ | ✗ | ✔ | ✔ | ✔* |
Root | ✔ | ✗ | ✗ | ✗ | ✔** |
* PostgreSQL supports has separate constructs for schemas and databases.
** PostgreSQL supports superusers but does not have a "root" user.