Nejc

quantumly.eth
not affiliated with @flashnet, ex-@kodexlabs

[Nejc @quantumly]

Currently exploring new opportunities 👀
DMs open if you're building cool things.

[Nejc @quantumly]

@andruyeung

[Nejc @quantumly]

Creating a dApp and looking for a reliable blockchain connection? Check out dRPC https://t.co/RbCMstc7Eq. #RPC # web3 # dRPC

[Nejc @quantumly]

@philosophymeme0 kafka diskless?

[brantly.eth @BrantlyMillegan]

BIG week for new features on @grailsmarket!
➡️ Grails is the best @ensdomains manager & market, https://t.co/fSiiTVqOmb

✅ Grails Chat 💬
- Message any Ethereum account on the Grails app
- Easier negotiation between sellers and buyers
- Try it out: message me (brantly.eth) and say hi and i'll message you back! 🤝

✅ Comments 🗣️
- Public comments section on all name pages
- Name owner gets a notification!

✅ New ENS metadata service 🪪
- We built our own service to generate NFT images for ENS names
- Images should load much faster!
- Different colors for Registered, Premium, Available, Grace, w/ nice transitions

✅ Bulk Search page 🔎🔎🔎
- Grails has long had bulk search, up to 10k terms, built into the normal search
- This is a dedicated Bulk Service page with a large input box
- Find it in the More navbar menu, alongside Live Activity, Analytics, Leaderboard

[Nejc @quantumly]

@kohlidoteth ser do you have a loicense for that gradient

[Nejc @quantumly]

@claudeai What did it suggest after its 3rd failure?
To make a new chat which is how we ended up with the post that started this thread

[Nejc @quantumly]

Yo @claudeai I know you're trying to give users worse and worse models whilst calling them the same but cmon... Opus 4.6 running research for 20 minutes then naming a report "The longest research report in history appears to be empty[...]" is just cruel

[Nejc @quantumly]

@claudeai Its not the first time... I thought the "Let me redo it properly now." would do something but nope!
Maybe 3rd times the charm? Wrong again

[Nejc @quantumly]

@pontusab Any plans to support savings accounts and pockets with Revolut? It seems to just name all accounts the same and not include Flex Savings for instance

[Nejc @quantumly]

vibing to a mix by @gakonst
why didnt I know paradigm is also a crew
https://t.co/5bx1f4nhqF

[Nejc @quantumly]

@om_patel5 https://t.co/5I43H1Upvx

[Nejc @quantumly]

Ever wanted to have your agent query @spark ?
https://t.co/P81V2BJZaZ

[RisingWave @RisingWaveLabs]

Rewriting Debezium in Rust sounds like the obvious move. We didn’t do it.

And that decision matters more than you think.

An in-depth look at our CDC strategy.

Covering:
Architecture decisions
Tradeoffs
Ecosystem realities
Custom engineering

RisingWave’s core compute and storage engine is written in Rust.

So people ask:
“Why not build a Rust-native CDC engine and replace Debezium?”

We tried prototypes and tests.

Our decision:

Do not rewrite Debezium. Embed and customize it instead.

CDC is more than a parser.

CDC is ecosystem-heavy:
Debezium is the de facto standard
Connectors for Postgres, MySQL, SQL Server, etc.
Years of fixes for edge cases, encodings, DDL, and versions
Active community tracking database evolution

A Rust rewrite would try to rebuild that ecosystem and its maintenance.

Why Embedded Debezium, not Debezium Server?
We chose the Embedded Engine:

Server mode
Separate process that reads from DB and writes to Kafka or Pulsar
Generic forwarder, hard to deeply customize

Embedded mode
Java library inside our process
We pull CDC events via API and control buffering, transforms, backpressure, and errors
CDC runs inside RW with the same scheduler, checkpoints, monitoring, and alerts

This keeps CDC aligned with RisingWave’s streaming DAG and recovery model.

What we built on top of Debezium?

Embedding Debezium lets us upgrade behavior where it matters most:
Lock-free snapshot + incremental stitching
Record a snapshot boundary, stream snapshot rows and WAL or binlog events together, then deduplicate downstream for a consistent initial state without long locks.

Parallel backfill for large tables
Slice big tables by primary key ranges, backfill in parallel, and adapt thread count to upstream DB load for faster copy without overload.

Cross-cloud schema history
Pluggable history for S3, GCS, Azure Blob, etc, fitting multi-cloud deployments, migrations, and failovers.

Memory-aware schema history
Segment history by size or time and load only what is needed, reducing memory peaks and stabilizing long-running CDC.

TOAST column completion for Postgres
When Debezium sends __debezium_unavailable_value, we fetch the historical TOAST value and merge it back so rows stay complete.

Instant schema change detection
Use PostgreSQL Relation messages from the replication protocol for near real-time schema sync with fewer metadata polls and less DB load.

All of this is possible because Debezium runs inside RW, not as an external black box.

Pragmatism over rewrites!
Debezium gives us maturity, widely used connectors and battle-tested log parsing.
A Rust rewrite would be multi-year, high-risk maintenance with limited gain over embedding and extending Debezium.

What we needed was a stable, controllable, deeply integrated CDC entry point for RW, not a brand new CDC ecosystem.

So our choice:
Use Debezium Embedded Engine as the foundation
Customize where our workloads demand it
Focus on engineering efficiency, stability, and maintainability instead of rewriting everything in Rust for its own sake.

[Nejc @quantumly]

@akuchibotla great mentality, sent an email

[Nejc @quantumly]

@skillissuesf Value 📈

[Nejc @quantumly]

@skillissuesf holy AGI

[Nejc @quantumly]

@AlliumLabs spark wen

[Nejc @quantumly]

@generalbreadco Is there a way for websites to use the wallet? Would love to try it