Handling Serialization

You do not need to create serializers for the messages, events, or the state of Kalix components but you need to make them serializable. The same is true with Kalix endpoints. Kalix exposes the inputs and outputs of endpoints as JSON and you need to make them serializable. You have two ways to do this.

  1. If you are using Java record then no annotation is needed. It just works. It’s as simple as using record instead of class. Kalix leverages Jackson under the hood and makes these records serializable for you.

  2. If you are using Java class then you need to annotate them with the proper Jackson annotation.

When consuming Messages from Topics

When consuming events from a topic deserialization works out of the box. By default Kalix serialize Java objects to JSON when publishing to a topic, or when emitting events from an entity, whatever they are value changes or snapshots. Therefore it can deserialize them as JSON when consuming them.

When subscribing, you can use as the input of your subscribing method the event class or record. In the following example you can see how the actions are subscribed to ValueIncreased and ValueMultiplied.

import kalix.javasdk.action.Action;
import kalix.springsdk.annotations.Subscribe;

public class CounterTopicSubscriptionAction extends Action {

    private Logger logger = LoggerFactory.getLogger(CounterTopicSubscriptionAction.class);

    @Subscribe.Topic(value = "counter-events") (1)
    public Action.Effect<Confirmed> onValueIncreased(ValueIncreased event){ (2)
        logger.info("Received increased event: " + event.toString());
        return effects().reply(Confirmed.instance); (3)

    @Subscribe.Topic(value = "counter-events") (4)
    public Action.Effect<Confirmed> onValueMultiplied(ValueMultiplied event){ (5)
        logger.info("Received multiplied event: " + event.toString());
        return effects().reply(Confirmed.instance); (6)
1 subscribing to the ValueIncreased from topic 'counter-events'.
2 setting the method input type to the events produced by the counter.
3 any return is valid.
4 subscribing to the ValueMultiplied from topic 'counter-events'.
5 setting the method input type to the events produced by the counter.
6 any return is valid.

As we mentioned it works out of the box.

Receiving CloudEvents

Kalix uses the CloudEvents standard when receiving from and publishing to topics. The CloudEvents specification standardizes message metadata so that systems can integrate more easily.

Describing the structure of the message payload is the CloudEvents feature most important to Kalix.

An example of that is the capability to send serialized JSON messages and have Kalix deserialize them accordingly.

To allow proper reading of JSON messages from external topics, the messages need to specify the message attributes:
  • Content-Type = application/application-json

  • ce-specversion = 1.0

  • ce-type = fully qualified name (e.g. com.example.ValueIncreased)

(The ce- prefixed attributes are part of the CloudEvents specification.)