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 1
Programming languages > DAGs for workflow engines. We agree, and it's exactly why we built version-safe, durable workflows into Platformatic for @kubernetesio. Nice shoutout from @pranaygp on the @vercel blog.
Pranay Prakash
@pranaygp
Aug 28
Wrote a 'lil post on a brief history of the workflow sdk vercel.com/blog/the-best-…
2
Platformatic
@platformatic
Sep 11
𝐀 𝐧𝐞𝐰 𝐛𝐚𝐧𝐭𝐞𝐫 𝐞𝐩𝐢𝐬𝐨𝐝𝐞! What if you could execute a package without ever unzipping it? What if npm had no central server, just a peer-to-peer mesh with cryptographic integrity baked in? No slides, no answers, no agenda.
Luca Maraschi and Matteo Collina
1
Platformatic
@platformatic
Sep 10
"We're not done yet. Once we complete the last three or four improvements, we think we can get our Node.js system to 500–600 MB/s per second per container." Fabrizio Fenoglio, @supabase Currently at 300. Target: 500–600. No new hardware. Same architecture, pushed further.
Supabase and Platformatic
1
Platformatic
@platformatic
Sep 9
@vercel 's engineering blog: "The best workflow engine is a programming language." We couldn't agree more! it's the whole idea behind Platformatic's durable, version-safe workflows for @kubernetesio, cited in the piece as a working example.
3
Platformatic
@platformatic
Sep 7
"50 MB/s per core, having a very hard time keeping up. Now we're running 300 MB/s per container with 2 cores — we've halved the number of containers we run." Fabrizio Fenoglio, @supabase 4x throughput. Half the infrastructure. Flat GC. No latency spikes.
2