Antwnis

That's a great example ^ that demonstrates exactly how this vulnerability can be easily abused

I love how a real-life experience helped a team innovate and shape a product aiming at improving data platform engineering as well as data ethics!

Lenses.io user & data experience is at a totally new level .. feels like using Slack / but for real time data - and makes hard techs like Kafka & Kubernetes such a pleasure to work with !

It's quite interesting how Lenses blends the streaming data fabric with the application layer!

Lenses.io | UI/UX Developer | London | Full-time

Lenses a leader in DataOps is looking for an ex-engineer who can now look beyond the UI, and design excellence in the user experience.

We are a high growth startup based in London with a distributed team building something really cool

Contact us at [email protected] and meet us in Old Street

> How exactly do you "forget" the data on the logs?

If we think around the options, you can have either:

i) eventual deletion (log retention policy) ii) compacted topics (and push null values) iii) expensive re-processing of the entire log iv) expensive segment re-write operation

with each option bringing in a new set of challenges

As everything in life, to gain something, you need to sacrifice something else. With RDBMS you get mutability; but to go 10x or 100x faster/larger you need to make hard decisions.

HDFS, S3 and other systems have immutability in-built. Immutability is not bad per-se, as it give (some) assurance that data has not been tampered with, and although it could be implemented, the system cost could be significant.

Stricking the right balance is the challenge