Use cases

While NotoDB is suitable for applications that have high read demands, it should not be used in applications that require high-frequency, asynchronous writes to the database.

NotoDB uses Amazon S3 for its storage engine. Because S3 does not allow for partial file writes, writing new items or updating existing items requires a full update of the item's parent set.

Recommended uses for NotoDB

  • Applications that require infrequent, synchronous database writes
  • Content management of a website
  • Simple object storage required as part of an application
  • A simplified REST API for your S3 buckets

Discouraged uses for NotoDB

  • Applications that require frequent, asynchronous writes
  • User data / account management
  • Application data storage triggered by user or system behavior

NotoDB is a great solution for folks looking to leverage a simple data layer in the cloud without the expense of the underlying hardware required of traditional database solutions such as MySQL, PostgreSQL, MongoDB, etc.

Next articleAuthentication