History and Roadmap

A quick overview of where we've been and our plans for the future

ACA Control.net (2008 - 2012)

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

ACA Control V1 (2012 - 2014)

First commercial release. Proved the model and highlighted limitations

• 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.

ACA Engine V1 (2014 - 2018)

Current release. Re-architectured for performance and scalability.

• Reactor per CPU core + thread pool
• Database: Couchbase + ElasticSearch
• Authentication: *any
• Language: Ruby

Engine V1 and V2 are 100% compatible at both a driver and database level.

ACA Engine V2 (2017 - ...)

Improved reactors, database adaptors and more flexible multi-node scaling.

• 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

ACA Engine Next

Multi-process and make use of compiled code without compromising our goal of live updates.

• Language: Ruby and Crystal Lang
• Database: Couchbase + ElasticSearch OR Couchbase Lite Core
• Authentication: *any