Roadmap

Not built yet

• Planned

  Client libraries are planned for after 1.0. None has shipped, and this site carries no code sample in any language other than HQL.

• Planned

  Server-side grouping and multi-document atomicity are not planned for 1.0.

• Planned

  A published benchmark is planned. There is no head-to-head measurement in the repository today, so this site publishes no performance number at all.

• Planned

  The source will be published when hoardDB reaches v1.0.

  The repository is not public yet: the history is being prepared for publication first, so until it is there is nothing to clone.

• Planned

  Changing a store's type after it is declared is not built. It is planned for a later release.

  Until it lands, a store's type is fixed when you declare it: add a field of the type you want, copy the elements across, and drop the old field.

• Planned

  Copying data between nodes is not usable end to end yet. That covers replication, seeding a node that joins a cluster that holds data, and databases with more than one copy.

  join is refused once any database exists, so form the cluster first and create data after. Until this is built, do not count on a second copy of anything.

• Planned

  Pushing to a heap store and putting to a blob store are not available in ring mode yet. A large blob is planned to go up in chunks under one upload id.

  A heap store reads with peek, list, count and pop, and a blob store can be counted. Both can be declared.

• Planned

  A timeline read is planned: one request that reads the newest elements of many documents' stores together, such as a merged feed.

  Until it lands that is one request per store. A batch carries writes only.

• Planned

  Dropping a database or a bucket is planned to need its name typed to confirm, the same for every client. This is decided and not built.

  Today drop bucket runs at once with no prompt, and drop database is not available in ring mode.

• Planned

  Indexes declared when a bucket is created, and unique indexes, are planned for ring mode.

  Until they land, a list with a filter reads every document of the bucket.

• Planned

  Encryption at rest is planned for ring mode.

  Today a node with encryption at rest on does not serve ring mode, and says why in its log.

When not to use hoardDB

That page is not written yet. Until it is, Limitations lists what the shipped product does not do.