frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Confidential Cloud Public Beta

https://confidential.ai/blog/confidential-cloud-beta
1•ameanasad•32s ago•0 comments

Anthropic raises record $81B in IPO at $1.5T valuation

https://www.reuters.com/legal/transactional/anthropic-prices-blockbuster-ipo-83-share-source-says...
1•JumpCrisscross•1m ago•0 comments

Anthropic IPO raises record $81.3B on strong AI demand

https://www.npr.org/2026/11/18/nx-s1-6046212/anthropic-record-ipo-price
2•madihaa•4m ago•0 comments

Intel signs first external customer for advanced 18A chips

https://www.cnbc.com/2026/11/18/intel-first-18a-foundry-customer.html
2•snikolaev•8m ago•0 comments

CobaltC vs. Rust (compiled with overflow checks)

https://github.com/strawberry9/CobaltC/tree/main/bench
1•SilentLambda•10m ago•0 comments

Show HN: Satelital – How I made a custom game engine for my indie game

https://spectralorbit.com/blog/satelital_game_engine
1•ellipticaldoor•10m ago•0 comments

Steve Yegge on AI Agents and the Future of Software Engineering

https://newsletter.pragmaticengineer.com/p/steve-yegge-on-ai-agents-and-the
1•duck•12m ago•0 comments

Madras School System and AI Learning Share Similarity

1•tesnorindian•17m ago•0 comments

Show HN: Pip – Your Git history puts you on a Performance Improvement Plan

https://github.com/littlestjames82-sys/pip-pip
1•ghostdevstudio•20m ago•0 comments

Ask HN: What positive impact has AI had in the past 5 years?

2•meredithbloom•23m ago•2 comments

Official Microsoft agent-framework PyPI package compromised

https://opensourcemalware.com/blog/agent-framework-pypi-compromised
3•jruohonen•27m ago•0 comments

Rust doubled on GitHub in the year agents started 40% PRs

https://hyscaler.com/insights/the-internet-is-getting-rusty/
2•royraghav28•29m ago•1 comments

Danish researchers find efficient solution to the four colour problem

https://via.ritzau.dk/pressemeddelelse/15284557/breakthrough-danish-researchers-find-efficient-so...
1•theanonymousone•29m ago•0 comments

Stickers on Buttons: Why South Korea's Suneung AI cheating patch won't hold

https://siwoo.lol/note/stickers-on-buttons/
1•siwoo•30m ago•0 comments

Microsoft's official Python agent framework hijacked to distribute malware

https://www.theregister.com/security/2026/11/18/microsofts-official-python-agent-framework-hijack...
1•MadrasTh0rn•32m ago•0 comments

Featherweight, flying robot carries its own sensors and computers

https://news.mit.edu/2026/featherweight-flying-robot-carries-its-own-sensors-and-computers-1118
1•geox•32m ago•0 comments

Wall Street Pledged to Mobilize $500B for Nvidia–But Hasn't Put Up a Dime

https://www.wsj.com/finance/wall-street-pledged-to-mobilize-500-billion-for-nvidiabut-hasnt-put-u...
1•JumpCrisscross•35m ago•0 comments

Every one of my "show" posts is removed immediately

2•selectedambient•36m ago•1 comments

Show HN: Port.fm – Internet radio tuned by decade, energy, or location

https://port.fm/
1•fozuse•37m ago•0 comments

Nvidia Chips Ended Up Within Reach of China's Military

https://www.nytimes.com/2026/11/18/technology/nvidia-alibaba-china-military.html
2•JumpCrisscross•37m ago•1 comments

Towards Universal Data-Efficient Pretraining

https://qlabs.sh/research/applications/
1•Klaster_1•38m ago•0 comments

Show HN: Why Zero to One's Thesis Falls Short with Healthcare

https://davidngo1562.substack.com/p/its-not-about-the-money-until-it
1•illidan1000•41m ago•0 comments

The smart money is selling equity

https://www.acadian-asset.com/investment-insights/owenomics/the-smart-money-is-selling-equity
2•shoo•42m ago•0 comments

Turning one photo into a Goodbye GTA 5 AI video

https://gta5goodbyeai.com/
1•visiohex•43m ago•0 comments

Google Embraces Geothermal Technology to Vaporize Rock for Clean Power

https://www.wsj.com/business/energy-oil/google-embraces-geothermal-technology-to-vaporize-rock-fo...
1•gmays•49m ago•0 comments

As Meta bets big on Muse AI agent, early safety mishaps surface

https://www.reuters.com/investigations/meta-bets-big-muse-ai-agent-early-safety-mishaps-surface-2...
2•spenvo•50m ago•0 comments

Fluent Interface in C – Look ma, no this

https://opensource.googleblog.com/2026/11/fluent-interface-in-c-look-ma-no-this.html
1•matt_d•53m ago•0 comments

Signs of Eagle Predation on a 22-Kg Adult Primate

https://onlinelibrary.wiley.com/doi/10.1002/ajpa.70377
1•gumby•55m ago•0 comments

Email Encryption

https://computer.rip/2026-07-19-email-encryption.html
1•fagnerbrack•55m ago•0 comments

Show HN: The FODMAP mistake most health writers make

1•kouautomation•56m ago•1 comments
Open in hackernews

Show HN: ReJot – Database replication framework aimed at developers

https://github.com/rejot-dev/rejot
9•WilcoKruijer•1y ago
Hi Hacker News! We're Jan & Wilco from ReJot (https://rejot.dev). With ReJot we're building a framework that turns the write-ahead log of your database into an asynchronous communication channel for your services. ReJot enables application developers to define how the database tables they own should be replicated to other databases. Something we wish we had at in our previous job at a large fintech.

There is a gap between building internal (REST) APIs and Kafka (event streaming) to share data between services.

Internal APIs start to break down when you have more than a couple services communicating. Their synchronous nature makes them brittle in a distributed system: failures cascade and latency adds up. Companies operating internal APIs at scale often face challenges like managing implicit schemas and versioning. They also need to write significant amounts of code to implement features like circuit breakers and internal load balancing.

Event streaming addresses these issues by using asynchronous communication, but it also introduces significant drawbacks. Kafka is known for its operational complexity and high cost. Engineers must manage outbox tables, outbox processors, and consumers, which makes the system more difficult to understand and maintain.

ReJot is the middle ground solution that re-uses a database system's write-ahead log as an asynchronous communication channel. The WAL is well-suited to double as an outbox, this has been proven by CDC systems like Debezium. ReJot is a lightweight addition to existing infrastructure, and even re-uses existing (relational) database systems to store messages (temporarily) before sending them to the destination/sink databases.

We're developer focused, as opposed to being infrastructure focused. Much like how developers define the database table schemas they use, we enable developers to say how their data should be published to others in the distributed system. This is done through something we call "Public Schemas", they consist of a schema and a (SQL) query. When an item in the underlying table changes, the query is executed to produce an object conforming to the schema. This data is then forwarded through ReJot, ready to be consumed by a different service using a "Consumer Schema". This is again a simple (SQL) query that contains an INSERT statement. All of this is defined from within the codebase of the application, much like how ORMs or query builders work.

In short, ReJot re-uses your database in two ways: by consuming the WAL, and also by using queries to encapsulate and integrate data. This makes ReJot a good middle-ground between the brittleness of synchronous communication and the complexity of event streaming.

Excited to hear what you think!

Comments

raoulritter•1y ago
I'm thinking that now with all these agent to agent frameworks this could potentially work for that. If you send off one agent you want them to keep up to date and sync / talk to each-other. Could your solution work for something like A2A by google or similar to enhance the synchronization across the different agents doing their tasks and prevent them from landing in a loop or similar.
WilcoKruijer•1y ago
I'm not too familiar with how people store the state of AI agents, but I do think there's some opportunity to use ReJot for this use case. Hooking up an agent to ReJot and giving them access to all available Public Schemas could be an interesting way of letting an agent explore and use the data in a distributed system.
jasonthorsness•1y ago
If the consumers stall, doesn't the WAL have to grow in unbounded fashion? Does it place any backpressure on the writers?
WilcoKruijer•1y ago
You're right. Since we don't want to put too much pressure on the source database, we do save the (transformed) WAL items in an intermediary database (we call this the event store), so the source can clear its WAL.

This does mean the intermediary database can grow in an unbounded fashion. The use case really determines if this is fine or not. Since our focus right now is on (micro)service communication, we think this is fine in most cases, as the throughput usually is not gigantic.

Since the event store is just a Postgres database, it's easy to set up partitions to only retain data for a certain amount of time. On the near-term roadmap we also have back-fill support which will make it easier to work with shorter retention windows.