flâneur

Aeron Cluster - The Aeron Files

theaeronfiles.com · 1,348 words · saved by 1 readers

Documentation for Aeron based on the underlying files

Aeron Cluster Traditional Service ¶ We all recognise a 'traditional' service that looks something like this: Clients send in messages. The service processes them, builds up some internal state and sends response messages. Any modifications to the state are also written to a database, so if the service crashes, the state isn't lost. This is fine for moderate loads, but the database is a source of contention, so it becomes a bottleneck as the load increases. This kind of architecture will never be able to process 100,000's of messages per second with consistent, 99.999% latency measured in

related reading