Hiroyuki Yamada (@feeblefakien) profile picture

CTO @ https://teapawt.org/t.co/rAGiVb3GxQ. The original creator of ScalarDB and ScalarDL. Love database systems, parallel and distributed systems, skateboarding, and music.

Tokyo
Joined September 2023
Hiroyuki Yamada retweeted
SagaやTCCのオーケストレーションエンジン「ScalarDB Saga」をリリースし、Apache License 2.0で公開しました! github.com/scalar-labs/scala… ScalarDBは2PCに加えてSaga/TCCにも対応し、マイクロサービスやアプリケーション連携で、より幅広く活用できるようになりました。
9
1
15
1,506
Replying to @scalar_labs_en
ScalarDB doing transactions across databases that were never meant to talk to each other is an underrated problem. Most enterprises are stuck with five systems of record and no way to keep them consistent. Would you come on my podcast to talk about it? linktr.ee/evankirstel
1
5
4
221
ScalarDB can now manage microservices' data consistency using major approaches like Saga, TCC, and 2PC. For all approaches, we take modern/state-of-the-art techniques. Also, they are open-sourced under Apache 2. github.com/scalar-labs/scala… (2PC) github.com/scalar-labs/scala… (Saga and TCC)
I'm excited to announce the release of ScalarDB Saga, a modern orchestration engine for managing distributed transactions across microservices using Saga and TCC. It is now available as open-source software under the Apache License 2.0. github.com/scalar-labs/scala…
6
8
328
I'm excited to announce the release of ScalarDB Saga, a modern orchestration engine for managing distributed transactions across microservices using Saga and TCC. It is now available as open-source software under the Apache License 2.0. github.com/scalar-labs/scala…
4
1
5
590
"Saga is decentralized. 2PC is centralized." Mostly a myth. 2PC needs a coordinator. Orchestration-based sagas need an orchestrator. Choreography-based sagas need a message broker. All three have a center that must be up. New bonus piece: linkedin.com/pulse/saga-dece…
2
3
141
Stop solving microservice consistency in your application code. AI writes much of that layer now, and it mostly works. But "mostly" isn't "correct" — and the people closest to the code usually can't tell the difference. Series finale 👇 linkedin.com/pulse/stop-solv…
5
7
226
"Saga or 2PC?" is the wrong question. The right one is per operation: what does this piece of work actually need? A real system needs both — and most of the case against 2PC is really a case against one 30-year-old implementation. New post 👇 linkedin.com/pulse/stop-aski…
5
6
217
"Just use Saga, avoid 2PC." The default advice for consistency across services. I think both halves are too simple. Inside one DB, "all or nothing" is free. Across services, it isn't. New post on why the framing gets both sides wrong 👇 linkedin.com/pulse/more-free…
5
7
237
"Don't reach for microservices too early — start with a monolith." For most of the last decade, that was the right call. I think AI is quietly changing it. I wrote up why, as Part 1 of a new series, Architecture in the AI Era. 👇 linkedin.com/pulse/start-mon…
6
7
200
The CDMS workshop @VLDBconf'26 is being held in September in Boston, USA. It's a great place to share your data-related work that cares about composability, reusability, and modularity. We welcome your submissions for short papers and lightning talks. cdmsworkshop.github.io/2026/
3
6
180
ScalarDB (Cluster) is now Red Hat certified! catalog.redhat.com/en/softwa… Red Hat certified products are tested to meet Red Hat’s criteria and supported as defined in the Red Hat Collaborative Support Process. #ScalarDB #RedHat
3
1
6
2,153
This paper doesn't refer to the ScalarDB paper (VLDB'23), which achieves similar concurrency control decoupling, although it refers to Cherry Garcia and Epoxy. I think it's intentional and citation malpractice... vldb.org/pvldb/vol16/p3768-y…
Vol:18 No:9 → Concurrency Control as a Service vldb.org/pvldb/vol18/p2761-z…
6
14
1,080