History and Roadmap
A quick overview of where we've been and our plans for the future
No official release. Was designed to support all the .NET supported languages, including IronRuby.
- Thread pool with queues and job stealing
- Language: .NET Framework and Silverlight
First commercial release. Proved the model and highlighted limitations of the then design
- Single reactor thread + thread pool
- Database: SQLServer, PostgreSQL or MySQL
- Authentication: LDAP
- Language: Ruby
ACA Control drivers would run on ACA Engine, however there was no direct data migration.
Re-architectured for performance and scalability.
- Reactor per CPU core + thread pool
- Database: Couchbase + ElasticSearch
- Authentication: *any
- Language: Ruby and jRuby
Engine V1 and V2 are 100% compatible at both a driver and database level.
Current release. Improved reactors, database adaptors and more flexible multi-node scaling, among other features.
- Reactor per CPU core + first class fibers
- Thread pool remains only as a tool for drivers
- Database: Couchbase + ElasticSearch OR Couchbase Lite Core
- Authentication: *any
- Language: Ruby, jRuby and Rubinius
Multi-process and make use of compiled code without compromising live updates.
- Language: Ruby and Crystal Lang
- Database: Possible migration to Datanet
- Authentication: *any