Skip to content

FalconDB

FalconDB is fast and reliable key-value and file database. It stores the data in memory and to the disk. FalconDB provides HTTP API for all operations. It can be used on one node for small applications, and in multinode deployments with data redundancy and multitenancy.

Multinode

FalconDB can be deployed in multinode mode on Onteon. Onteon is a distributed application platform that manages deployments of all FalconDB services, providing also health checking and self-healing. FalconDB can also provide multitenancy with multiple separated database microservices for applications. High availability of FalconDB and advanced proxying can be provided by Onteon Tech HA Load Balancer.

FalconDB standalone schema

FalconDB multinode and multitenancy on Onteon

Onteon microservice

Onteon microservice version of FalconDB, contains .tar.gz file, which is ready to be deployed as Onteon application.

FalconDB on Onteon schema

One FalconDB instance Onteon deployment

Standalone microservice

Standalone microservice version of FalconDB, consists of:

  • .jar FalconDB Java file
  • JDK, so the application can be run without a need to install Java on the machine
  • start/stop/terminate scripts to manage FalconDB easily

This version runs without Onteon platform.

FalconDB standalone schema

One FalconDB instance standalone simple deployment

Advantages of FalconDB

  • Easy installation and configuration - FalconDB is one microservice
  • Easy to use for developers with simple HTTP API
  • Fast application development and full developer control on the scheme
  • Very fast - all operations are in-memory
  • Flexible - schema-less, stores JSONs and files
  • Portable to any Linux in x86/aarch64 architecture
  • Simple licensing

Capabilities

  • Storing data in memory and copying to persistent storage in asynchronous mode
  • Chunking or streaming large files
  • Persistent and temporary tables for ephemeral data
  • Read locks for reading - blocking data to be modified on a database level
  • Health checking end point
  • Autorotation - automatic maintenance of database size
  • Garbage collector keeping the cache at a constant size
  • Readable configuration - all parameters in one yaml file
  • Barriers - support blocking of data for asynchronous operation