The Exocomm Applications Programming Interface (API) lets you generate high-performance machine code applications based on Exocomm's library. It's a commercial product.
The Exocomm API libraries allow easy not only SQL integration with three different SQL storage engines : the native Exocomm SQL engine, SQLite, and MySQL. We can easily add plug-ins for
other types of SQL database if we notice a user demand for it. This gives you a lot of nice, easy options when you want to integrate your Exocomm software with SQL services nd best of all, you dont have
to re-write code to support new database types. For example, you might want to consult a third-party service for unknown records, keep a cache of used records locally, then migrate the data back to the
cloud when its no longer needed. Use multiple types of database instance even simultaneously.
Writes (INSERTs and UPDATEs) are performed on all available storage engines.
Reads (SELECTs) are performed in order of priority first the native engine, then SQLite, then MySQL (this is configurable).
The native Exocomm data storage engine requires absolutely zero third-party code, has a small memory footprint, and has excellent overall performance. It however lacks some features
desired in a full-featured SQL database, and some fancy operations (like indexing and replication) can be relatively slow. This storage engine is always enabled, and is used by default.
SQLite is a good choice for embedded devices or situations where you have a limited number of clients accessing the database. The code is compact and efficient (but still larger than the
Exocomm API), while providing most SQL functions programmers will need. It is connectionless, but the Exocomm API looks after locking, so youll have no trouble using it in multi-threaded applications.
This storage engine is optional. This storage engine is optional and must be enabled at compile-time. Special attention is needed (block-level replication) when multiple servers are writing to the same
And of course, MySQL is still the most popular choice for a fully-featured SQL server (it works fine with MariaDB or RDS, too). Use MySQL when you need full remote connectivity, user-based privilege
management and other fancy features. This storage engine is optional and must be enabled at compile-time. Specify your credentials in the API configuration file in /exocomm/local.
READ_TABLE ( THE_DATABASE_TO_READ , THE_TABLE_TO_READ )
This function SELECTs SQL rows.
WRITE_TABLE ( THE_DATABASE_TO_WRITE , THE_TABLE_TO_WRITE )
This function INSERTs or UPDATEs SQL rows.
DESTROY_TABLE ( THE_DATABASE_TO_DESTROY , THE_TABLE_TO_DESTROY )
This function deletes SQL rows.