Multisite distributed model on cloud or hybrid deployments using eventual system.

Causal consistency

Dalet blog reference: The deployment conundrum: cloud vs on-premises – why not both?

Flex Multisite distributed model on cloud or hybrid deployments using eventual system to replicate across multi-repositories for micro-services architecture.

Technical requirement summary highlights:

• Eventual bidirectional synchronization of multiple datacenters

• Replicate multiple SQL/NO-SQL data repos in a micro-service arch

• Resolve complex data dependencies and local unique ids across sites

• Large volume of entities and event processing

• High performance replication processes with scalable system

• Causal consistency and conflict resolution for event replication

• Self-monitoring and recovery life cycle using canary messages to validate actual system working across multi layers

• Auto-resync mechanism using data partition and comparison across multiple repositories for synchronization after outages

For good or for bad, the fact is that the architecture of a complex platform end up stacking directly/indirectly dependent layers of systems and subsystems.

Even though they are de-coupled and in theory independent things get interesting when such systems are stressed in high-volume/high-performance scenarios. Having a macro system that tries to replicate at low level the system consistency while guarantying top level use experience is a fun system.

Reminder the “when things go wrong …” requirement.