The Talon Manual

Skip to end of metadata
Go to start of metadata

The following sections discuss some of the more advanced usage patterns of working with Talon such as techniques for achieving zero garbage in your application, that in some cases require greater attention to detail in coding practices. 

Achieving Zero Garbage

Talon supports zero garbage steady state operation for applications that run with Event Sourcing as an HA policy. For low latency applications, avoiding creation of garbage or object allocation is desirable because that will result in GC pauses that cause latency spikes. In some applications, even a minor gc pause that results from promoting newly allocated objects to the tenured generation would violate SLAs. This section discusses the techniques application developers can apply to ensure that

Environment Replication

When working with Event Sourcing, applications cannot make business logic decisions that affect recoverable state or the contents of outbound messages based on data in the local environmental or reference data that may be out of sync with backup instances. Doing so can lead to situations where a backup application instance makes different decisions than the primary instance that result in divergent state. Divergence of state can causes major problems if the backup takes over after a failure in t

  • No labels