All Classes and Interfaces
Class
Description
An Effect is a description of what Kalix needs to do after the command is handled.
Construct the effect that is returned by the command handler or a step transition.
A workflow effect type that contains information about the transition to the next step.
Retry strategy without failover configuration
Actions are stateless components that can be used to implement different uses cases, such as:
An Effect is a description of what Kalix needs to do after the command is handled.
Construct the effect that is returned by the command handler.
Context for action calls.
Creation context for
Action components.Low level interface to implement
Action components.Options for actions
Register an Action in {
Kalix} using an
ActionProvider.CloudEvent representation of Metadata.
An event sourced command context.
Command context for Replicated Entity.
A value based entity command context.
A value based workflow command context.
Root class of all contexts.
Represents a call to another component, performed as a forward, a side effect, or a
request-reply.
Root context for all contexts that pertain to entities, that is, things that are addressable via
an entity id.
Options used for configuring an entity.
Context for an event.
The Event Sourced state model captures changes to data by storing events in a journal.
An Effect is a description of what Kalix needs to do after the command is handled.
Construct the effect that is returned by the command handler.
Root context for all event sourcing contexts.
Low level interface for handling events and commands on an entity.
Root entity options for all event sourcing entities.
Register an event sourced entity in
Kalix using a
EventSourcedEntityProvider.Represents an HTTP response with more level control over the status code, content type and body.
Allows to specify dedicated strategy for JSON schema evolution.
Representation of JWT claims that have been validated and extracted from the bearer token of a
request.
The Kalix class is the main interface to configuring entities to deploy, and subsequently
starting a local server which will expose these entities to the Kalix Runtime Sidecar.
This Logback JSON layout uses the name `severity` (instead of `level`).
A message envelope.
Transport specific metadata.
A metadata entry.
Context that provides access to metadata.
Annotation to assign a @
JsonMigration implementation for a given class.A passivation strategy.
A principal associated with a request.
Basic principals that have no additional configuration.
A local service principal.
The principals associated with a request.
Step builder for defining a workflow step for Java protobuf SDK
ProtoWorkflow<S extends com.google.protobuf.GeneratedMessageV3>
Workflows are stateful components and are defined by a set of steps and transitions between them.
A counter that can be incremented and decremented.
A Map of counters.
Factory for creating Replicated Data objects.
ReplicatedEntity<D extends kalix.replicatedentity.ReplicatedData>
An Effect is a description of what Kalix needs to do after the command is handled.
Construct the effect that is returned by the command handler.
Root context for all Replicated Entity contexts.
Low level interface for handling commands on a replicated entity.
Root entity options for all Replicated Entities.
ReplicatedEntityProvider<D extends kalix.replicatedentity.ReplicatedData,E extends ReplicatedEntity<D>>
Register a value based entity in
Kalix using a
ReplicatedEntityProvider.A Replicated Map that allows both the addition and removal of
ReplicatedData objects.A replicated map that maps keys to values, where each key may be associated with multiple values.
A Last-Write-Wins Register.
Clock for register replication
A Map of registers.
A Replicated Set that allows both the addition and removal of elements in a set.
A Vote replicated data type.
A side effect.
Interface used to represent HTTP status code.
The supported HTTP error codes that can be used when replying from the Kalix user function.
Utility interface for trace context helper methods.
Context for view update calls.
Value Entities persist their state on every change.
An Effect is a description of what Kalix needs to do after the command is handled.
Construct the effect that is returned by the command handler.
Root context for all value based entity contexts.
Low level interface for handling commands on a value based entity.
Root entity options for all value based entities.
Register a value based entity in
Kalix using a
ValueEntityProvider.Kalix applications follow the Command Query Responsibility Segregation (CQRS) pattern (see https://developer.lightbend.com/docs/akka-guide/concepts/cqrs.html).
An UpdateEffect is a description of what Kalix needs to do after the command is handled.
Context for views.
Creation context for
View entities.Low level interface for handling messages in views.
Workflows are stateful components and are defined by a set of steps and transitions between them.
Write consistency setting for replication of state updates for Replicated Entities.