Platformatic

@platformatic

The platform bridging the gap between Node.js developers, operators, and wider business. So you can focus on building 🚀

platformaticHQ.com

Joined April 2022

Replies Reposts Media

Pinned
Platformatic
@platformatic
Sep 22
🔥 New paper is out! State Without a Landlord. A durable workflow's journal already has the shape of a peer-to-peer log: one writer, append-only, deterministic replay. We propose sharing it so running workflows can move, resume and be verified without a single owner.
2
Platformatic
@platformatic
Sep 25
🎙️ New banter coming up soon! The Sandbox Was Fine. JavaScript Wasn't! A discussion between @lucamaraschi & @matteocollina about why teams keep making this mistake and what a better design would look like. Wed. 30th. 8:00 AM (PT) | 5:00 PM (CEST)
The Sandbox Was Fine. JavaScript Wasn't
From streamyard.com
Platformatic
@platformatic
Sep 24
🎉 A new article is out now! Sizing your worker pool by CPU count alone is a common trap. On real production hosts, 'available' CPUs are rarely idle. Adding more workers often reduces throughput instead of increasing it.
Matteo Collina
1
Platformatic
@platformatic
Sep 21
Ten requests could be ten cache hits or ten heavy renders. Same count, totally different load. The ICC Planner skips request counts and learns from Event Loop Utilization and heap signals instead the stuff that actually reflects what your app is doing. blog.platformatic.dev/introducing-th…
Luca Maraschi
@lucamaraschi
Sep 21
Ten requests could be ten cache hits. Or ten heavy renders that max out every core. Same number. Completely different load. Most capacity planning starts with request counts anyway, because they're easy to measure, not because they're right. The signal that actually matters is
Platformatic
@platformatic
Sep 18
🎙️ New Episode! Workflows function as an append-only log, and so does HyperCore. @lucamaraschi explored that line of inquiry and, as a result, produced a 50-page paper in which agent state is replicated peer-to-peer.
2