These are chat archives for atomix/atomix
We are no longer monitoring this channel, please join Slack! https://join.slack.com/t/atomixio/shared_invite/enQtNDgzNjA5MjMyMDUxLTVmMThjZDcxZDE3ZmU4ZGYwZTc2MGJiYjVjMjFkOWMyNmVjYTc5YjExYTZiOWFjODlkYmE2MjNjYzZhNjU2MjY
@digat we use everything but the primary-backup protocol (which is new) very heavily, and we’re in the process of deploying it in production in some very large networks. It is in production currently, but at a smaller scale than it will be by the end of the year. Currently all my time is invested in productionizing Atomix for large scale production deployments.
The Atomix Raft implementation in particular is stable and production ready. But the rest of Atomix 2.1 is actually in a state of flux right now. We’ve been in the process of refactoring the code base to consolidate our custom primitives, partitioning, protocols, etc in Atomix 2.1. That’s almost done, but Atomix 2.1 as a whole won’t be called production ready until we get it deployed in the same environments in which its various pieces are currently deployed.
Basically, Atomix 2.1 is the combination of a lot of code from Atomix and ONOS that’s currently being deployed to production, but don’t yet feel confident after the refactoring that it’s itself production ready.