When embarking on your Kafka journey, what's your first move?

Commonly, you'll seek the most effective way to visually explore everything happening your the Kafka universe.

Tools like Confluent Cloud, Conduktor, Lenses and AKHQ are excellent for this purpose.

Soon, you'll need more independence in your explorations, you'll want to dump all your data in your favorite database.
Get a database ready, set up Kafka connect, establish a connector to move all your topics, and you're all set.

Satisfaction comes quickly as you return to the world of SQL.
You can rely on your trusty existing ecosystem. In short: you're in a very good place.

But here's the catch: often, the security team enters the picture a bit too late...
... and suddenly, you're in a whirlwind of compliance issues involving GDPR, HIPAA, CCPA etc.

You are now tasked to introduce RBAC, ABAC, data masking, payload encryption, and maybe even crypto shredding in your Kafka security!

Since your target database probably lacks support for some of these features, you find yourself backed into a corner.

Not anymore!

Let me present a practical idea where you'll be able to get your SQL back, while supporting all these security constraints!

(If this approach wins you over, the fresh capabilities it brings to the table will be a pleasant shock.)