To stimulate insightful thinking and discussion, I'd like to present an opinion. I believe that tiered storage cannot save Kafka.
1. First, tiered storage does not fundamentally solve the issue of Kafka's cross-Availability Zone (AZ) traffic costs. This part of the traffic cost can cause a significant expenditure in the cloud. For reference, you can check out this link: https://www.confluent.io/blog/understanding-and-optimizing-y...
2. Essentially, tiered storage only alleviates the disadvantage of Kafka's partition data movement, but it does not eradicate it. Kafka requires the last logsegment of a partition to be on local storage. If this segment is large, a substantial amount of partition data still needs to be replicated during scaling.
Delve into the intricacies of various streaming platforms with our comprehensive comparison table. This table underscores how diverse technical architecture choices shape unique outcomes, carving distinct paths in the streaming landscape. We're eager to hear your insights and perspectives. What does this comparative analysis inspire in you? Let's spark some enlightening discussions!
Podlite indeed looks promising, especially with its extensibility and support for Markdown. I agree that if a markup language gets too complex, using raw HTML might be more advantageous. However, I think the strength of Podlite lies in its universality and flexibility, allowing it to adapt to various project requirements.
I'm particularly interested in the extensibility of Podlite. This feature allows the language's functionality to be expanded according to the specific needs of a project, which could be a huge plus in many cases. I look forward to seeing how Podlite evolves.
As for using raw HTML and JavaScript, while they indeed provide powerful querying features, Podlite might be simpler and more intuitive for those who are not familiar with these technologies. I think that's another strength of Podlite.
All in all, I think Podlite is a project worth watching. I'll keep an eye on its progress and look forward to seeing what changes it can bring in the future. Thanks for sharing this project!
I pay great attention to the appearance of a book when I buy it. From this point of view, this book suits my taste very well. I like the design of the cover and the slightly frosted texture.
1. First, tiered storage does not fundamentally solve the issue of Kafka's cross-Availability Zone (AZ) traffic costs. This part of the traffic cost can cause a significant expenditure in the cloud. For reference, you can check out this link: https://www.confluent.io/blog/understanding-and-optimizing-y...
2. Essentially, tiered storage only alleviates the disadvantage of Kafka's partition data movement, but it does not eradicate it. Kafka requires the last logsegment of a partition to be on local storage. If this segment is large, a substantial amount of partition data still needs to be replicated during scaling.