The Axual Platform 2024.4 Winter Release offers key updates including Data Masking, enhanced Kafka Streams, and Consumer Offset reset, empowering users with improved control, performance, and efficiency for better data management.

As the festive season draws to a close and we turn our attention to new beginnings and resolutions, we’re excited to unveil the Winter Release of Axual Platform 2024.4.
Winter brings a time for celebration, renewal, and reflection, and we’ve channeled this spirit into our latest update. With a dedicated focus on enhancing your experience, we’ve ensured the platform continues to evolve, meeting your needs while staying ahead of the ever-changing data landscape. This release incorporates valuable user feedback from the introduction of Data Masking in Self-Service to an enhanced Kafka Streams experience. It offers a more intuitive, efficient, and future-ready platform.
Whether you're new to Kafka or an experienced user looking to optimize your workflows, this update empowers you with greater control, deeper insights, and improved performance. Let’s explore the key highlights of the 2024.4 release and see how we’re setting you up for success in the next season of data challenges.
In this release blog, we cover the following topics:
This feature allows Schema and Topic Owners to define which fields of a Schema should be masked when performing a Topic Browse search on Kafka. It enables the selective hiding of sensitive or private data within Kafka topics.

The purpose of this feature is to ensure that certain sensitive information stored in Kafka topics is never exposed to users who browse the topic. By masking specific fields, organizations can protect sensitive data while still allowing users to interact with the rest of the topic content.
This feature is particularly useful for Topic Owners and Schema Owners responsible for managing the data within Kafka topics. It ensures they can enforce data security policies by controlling which information is visible to users.
In many cases, Kafka topics may contain sensitive information, such as personally identifiable data, financial details, or other confidential content, that should not be exposed to all users. With this feature, Topic and Schema Owners can configure data masking rules for specific fields within a schema. When users perform a Topic Browse search, any field marked for masking will be hidden, ensuring that users only have access to non-sensitive data. This feature enhances privacy and security while maintaining Kafka's flexibility and usability for broader data management and analysis purposes.

Here you can find the public docs for the Data Masking operation
This feature enhances the Kafka Streams experience by allowing the Kafka Streams application to automatically create intermediate topics through Self-Service, eliminating the need to manually create intermediate topics by the Application Owner.

The purpose of this feature is to simplify and streamline the process for Application Owners working with Kafka Streams. It reduces the time and effort spent manually creating intermediate topics, allowing the application to handle this task automatically making it easier and faster to deploy and manage Kafka Streams applications.
This feature is handy for Application Owners who work with Kafka Streams and must manage intermediate topics for their data processing pipelines. It is particularly beneficial for users who want to experiment or prototype with Kafka Streams without needing to pre-create multiple intermediate topics.
Kafka Streams applications often require intermediate topics to process data through different stages of a stream processing pipeline. Traditionally, Application Owners had to manually create these intermediate topics, which added complexity and extra steps to the setup process. With this new feature, Kafka Streams applications are able to automatically create the necessary intermediate topics during their execution. This eliminates the need for manual topic creation and reduces the overhead for Application Owners. The feature is especially useful for experimentation and quick iterations, as users no longer need to pre-configure topics before running their applications. It streamlines the workflow, enhances productivity, and accelerates the deployment of Kafka Streams applications, making it easier for Application Owners to focus on data processing without worrying about the infrastructure setup.
Here you can find the public docs for the Streaming Application
The "Reset Consumer Application Offset" feature allows Application Owners to reset the Consumer Group Offset for their Kafka application to either the LATEST or EARLIEST position. This enables a consumer to either skip to the latest available message in a Kafka topic or rewind to the earliest available message.

The purpose of this feature is to give application owners control over where a consumer should begin reading within an existing Kafka topic. This is particularly important when setting up new applications that need to consume from topics with large message histories but only need the most recent messages (or need to process all available data from the beginning).
This feature is useful for Application Owners and developers working with Kafka consumers who need to interact with topics containing large amounts of historical data. It is especially beneficial when new applications need to consume a Kafka topic with millions of messages, but only the latest messages are relevant for processing.
When consuming messages from a Kafka topic, Kafka maintains the offset for each consumer group, determining the point at which consumption resumes after a consumer restarts or recovers. In scenarios where an application is newly created to consume from a Kafka topic with millions of messages, it might not be necessary to process all historical messages, especially if only the most recent data is relevant.
This feature allows Application Owners to reset the Consumer Group Offset to the LATEST position, so the consumer immediately starts consuming new messages, bypassing older ones. Alternatively, if there’s a need to reprocess or analyze historical data, they can reset the offset to EARLIEST to start consuming from the beginning of the topic.
This capability is crucial for optimizing performance and ensuring that only the necessary data is consumed, saving resources and reducing unnecessary processing overhead. It also ensures flexibility in how consumers interact with topics based on changing application requirements or use cases.
In our release notes, you will find other, more minor, updates to our product, which we are continuously improving with your feedback.
Inspired by what you've read? Facing challenges with Kafka in an enterprise environment? We're here to assist. Here are your next steps: