Hi Wolfgang, it's a very interesting question, I would say it depends on your configuration. Ignite is a distributed database, so you always will have P in our equation, except corner case when you will run only one node on one host, in this case, no partition can happen. But really no one wants to get in a split bran situation when a divided(partitioned) cluster supports two sets of data and loses consistency as result, so you need to have SegmentationResolver set to avoid split-brain, so without it ignite provides AP. If you have SegmentationResolver or use ZookeeperDiscovery you get CP.(ZK by nature always has to have a quorum and as result provides us split brain protection of a box),
Thanks, Mike. On Tue, Dec 1, 2020 at 11:22 AM Wolfgang Meyerle < wolfgang.meye...@googlemail.com> wrote: > Hi, > > the CAP Theorem states that a database can only achieve two of the > following design goals: > > - Availability > - Consistency > - Partition Tolerance > > Which two of the above design goals Apache Ignite has been developed for? > > Mongo DB and Redis for instance match Consitency and Partition tolerance > but lack of the availability design goal. > > Regards, > > Wolfgang > -- Thanks, Mikhail.
