Login

Recent searches

No recent searches

Search options

Only available when logged in.
fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.8K
active users

fosstodon.org: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#rebuild

3 posts2 participants1 post today
Public
Alo Japan

alojapan.com/1267152/mitsubish Mitsubishi Heavy talks to 200 suppliers to rebuild Japan nuclear reactors #200 #Heavy #Japan #JapanNews #mitsubishi #news #Nuclear #reactors #rebuild #suppliers #Talks TOKYO — Mitsubishi Heavy Industries is in discussions with over 200 part suppliers with the goal of replacing nuclear reactors in Japan with a more advanced model, Nikkei has learned. The Japanese industrial group is currently developing an advanced light-water reactor it aims…

Mitsubishi Heavy talks to 200 suppliers to rebuild Japan nuclear reactors
Public
N-gated Hacker News

Ah, yes, the age-old question: "What if we could #rebuild #Kafka from scratch?" 🤔 Because nothing says "innovation" like recreating a decades-old messaging system for the 547th time. 🔄 Meanwhile, the rest of us are busy wondering why we can’t rebuild some common sense into software engineering conferences. 🙄
morling.dev/blog/what-if-we-co #Innovation #SoftwareEngineering #CommonSense #HackerNews #ngated

www.morling.dev · What If We Could Rebuild Kafka From Scratch? Update April 25: This post is being discussed on Hacker News, lobste.rs, and /r/apachekafka The last few days I spent some time digging into the recently announced KIP-1150 ("Diskless Kafka"), as well AutoMQ’s Kafka fork, tightly integrating Apache Kafka and object storage, such as S3. Following the example set by WarpStream, these projects aim to substantially improve the experience of using Kafka in cloud environments, providing better elasticity, drastically reducing cost, and paving the way towards native lakehouse integration. This got me thinking, if we were to start all over and develop a durable cloud-native event log from scratch—​Kafka.next if you will—​which traits and characteristics would be desirable for this to have? Separating storage and compute and object store support would be table stakes, but what else should be there? Having used Kafka for many years for building event-driven applications as well as for running realtime ETL and change data capture pipelines, here’s my personal wishlist:
ExploreLive feeds
About