Matteo Collina
@nodeland.dev
Platformatic.dev Co-Founder & CTO, Node.js TSC member, Lead maintainer Fastify, Board OpenJS, Conference Speaker, Ph.D. Views are my own.
Ever built a "simple" distributed system that turned into a 3 AM production nightmare? 💀
You started with Kafka (or RabbitMQ) and a few services. Now you're juggling retries, compensations, and correlation IDs like it's a circus act.
Time to talk about the workflow orchestration wars 🎧⬇️
You started with Kafka (or RabbitMQ) and a few services. Now you're juggling retries, compensations, and correlation IDs like it's a circus act.
Time to talk about the workflow orchestration wars 🎧⬇️
October 31, 2025 at 4:59 PM
Ever built a "simple" distributed system that turned into a 3 AM production nightmare? 💀
You started with Kafka (or RabbitMQ) and a few services. Now you're juggling retries, compensations, and correlation IDs like it's a circus act.
Time to talk about the workflow orchestration wars 🎧⬇️
You started with Kafka (or RabbitMQ) and a few services. Now you're juggling retries, compensations, and correlation IDs like it's a circus act.
Time to talk about the workflow orchestration wars 🎧⬇️
How it works is dead simple. Just add a permissions block to your Watt config . Your service can now ONLY access those paths. Try to read elsewhere? ERR_ACCESS_DENIED.
October 28, 2025 at 3:36 PM
How it works is dead simple. Just add a permissions block to your Watt config . Your service can now ONLY access those paths. Try to read elsewhere? ERR_ACCESS_DENIED.
🔒 We just shipped application-level file system permissions in @platformatic.dev Watt!
The simplest way to segregate your Node.js microservices - leveraging Node.js's native permission model to control exactly what files each service can touch.
Here's why this matters 🧵
The simplest way to segregate your Node.js microservices - leveraging Node.js's native permission model to control exactly what files each service can touch.
Here's why this matters 🧵
October 28, 2025 at 3:36 PM
🔒 We just shipped application-level file system permissions in @platformatic.dev Watt!
The simplest way to segregate your Node.js microservices - leveraging Node.js's native permission model to control exactly what files each service can touch.
Here's why this matters 🧵
The simplest way to segregate your Node.js microservices - leveraging Node.js's native permission model to control exactly what files each service can touch.
Here's why this matters 🧵
Example TypeScript fix:
October 22, 2025 at 3:59 PM
Example TypeScript fix:
The setup is simple. Thehe performance difference? Massive.
October 22, 2025 at 3:59 PM
The setup is simple. Thehe performance difference? Massive.
🚀 Noop Functions vs Optional Chaining: A Performance Deep Dive
I ran benchmarks comparing `noop()` vs `obj?.fn?.()` and the results surprised me.
Spoiler: Noop functions are 5.5x to 8.8x faster.
Here's what you need to know 🧵
I ran benchmarks comparing `noop()` vs `obj?.fn?.()` and the results surprised me.
Spoiler: Noop functions are 5.5x to 8.8x faster.
Here's what you need to know 🧵
October 22, 2025 at 3:59 PM
🚀 Noop Functions vs Optional Chaining: A Performance Deep Dive
I ran benchmarks comparing `noop()` vs `obj?.fn?.()` and the results surprised me.
Spoiler: Noop functions are 5.5x to 8.8x faster.
Here's what you need to know 🧵
I ran benchmarks comparing `noop()` vs `obj?.fn?.()` and the results surprised me.
Spoiler: Noop functions are 5.5x to 8.8x faster.
Here's what you need to know 🧵
🚀 New blog post: "From curl Commands to Type-Safe API Clients"
Ever copied curl commands from DevTools to reverse-engineer an API? What if you could turn those into production-ready, type-safe HTTP clients automatically?
Here's how 👇
Ever copied curl commands from DevTools to reverse-engineer an API? What if you could turn those into production-ready, type-safe HTTP clients automatically?
Here's how 👇
October 21, 2025 at 4:15 PM
🚀 New blog post: "From curl Commands to Type-Safe API Clients"
Ever copied curl commands from DevTools to reverse-engineer an API? What if you could turn those into production-ready, type-safe HTTP clients automatically?
Here's how 👇
Ever copied curl commands from DevTools to reverse-engineer an API? What if you could turn those into production-ready, type-safe HTTP clients automatically?
Here's how 👇
The best part? Zero configuration needed.
Just install and go. Auto-generates interactive HTML flamegraphs on exit. Click to zoom, explore call stacks, find those sneaky allocations.
Just install and go. Auto-generates interactive HTML flamegraphs on exit. Click to zoom, explore call stacks, find those sneaky allocations.
October 14, 2025 at 3:02 PM
The best part? Zero configuration needed.
Just install and go. Auto-generates interactive HTML flamegraphs on exit. Click to zoom, explore call stacks, find those sneaky allocations.
Just install and go. Auto-generates interactive HTML flamegraphs on exit. Click to zoom, explore call stacks, find those sneaky allocations.
Production-ready with Wattpm, the Node.js application server
Profile your live applications safely. Minimal overhead (~5-10%). Your users won't even notice.
Profile your live applications safely. Minimal overhead (~5-10%). Your users won't even notice.
October 14, 2025 at 3:02 PM
Production-ready with Wattpm, the Node.js application server
Profile your live applications safely. Minimal overhead (~5-10%). Your users won't even notice.
Profile your live applications safely. Minimal overhead (~5-10%). Your users won't even notice.
Real-world win: Finding memory leaks just got 10x easier
Before: Hours of debugging, adding console.logs, praying to the GC gods
Now: hammer your API endpoint → instant flamegraph shows the leak
Wide sections = memory hogs 📊
Before: Hours of debugging, adding console.logs, praying to the GC gods
Now: hammer your API endpoint → instant flamegraph shows the leak
Wide sections = memory hogs 📊
October 14, 2025 at 3:02 PM
Real-world win: Finding memory leaks just got 10x easier
Before: Hours of debugging, adding console.logs, praying to the GC gods
Now: hammer your API endpoint → instant flamegraph shows the leak
Wide sections = memory hogs 📊
Before: Hours of debugging, adding console.logs, praying to the GC gods
Now: hammer your API endpoint → instant flamegraph shows the leak
Wide sections = memory hogs 📊
🔥 BIG NEWS: @platformatic/flame and Watt Runtime now support heap profiling!
Finally tackle those memory leaks and optimize your Node.js apps with comprehensive insights into BOTH CPU time AND memory usage.
No more guessing where your memory is going 🎯
Finally tackle those memory leaks and optimize your Node.js apps with comprehensive insights into BOTH CPU time AND memory usage.
No more guessing where your memory is going 🎯
October 14, 2025 at 3:02 PM
🔥 BIG NEWS: @platformatic/flame and Watt Runtime now support heap profiling!
Finally tackle those memory leaks and optimize your Node.js apps with comprehensive insights into BOTH CPU time AND memory usage.
No more guessing where your memory is going 🎯
Finally tackle those memory leaks and optimize your Node.js apps with comprehensive insights into BOTH CPU time AND memory usage.
No more guessing where your memory is going 🎯
🎙️ NEW PODCAST: "Node.js Loves Python"
What if you could run Python ASGI apps inside your Node.js services? No proxies. No overhead. Just seamless integration.
@lucamaraschi & @matteocollina explore how @platformatic/python makes this possible 🚀
What if you could run Python ASGI apps inside your Node.js services? No proxies. No overhead. Just seamless integration.
@lucamaraschi & @matteocollina explore how @platformatic/python makes this possible 🚀
October 13, 2025 at 4:43 PM
🎙️ NEW PODCAST: "Node.js Loves Python"
What if you could run Python ASGI apps inside your Node.js services? No proxies. No overhead. Just seamless integration.
@lucamaraschi & @matteocollina explore how @platformatic/python makes this possible 🚀
What if you could run Python ASGI apps inside your Node.js services? No proxies. No overhead. Just seamless integration.
@lucamaraschi & @matteocollina explore how @platformatic/python makes this possible 🚀
Nobody would ever call internal functions directly. But the damage was done.
October 10, 2025 at 3:59 PM
Nobody would ever call internal functions directly. But the damage was done.
🛠️ The secret sauce:
- Rust-powered http-handler crate for zero-copy bridging
- WebAssembly-based binary patcher for Python library loading
- Thread pool management for Python workers
- Full ASGI protocol support
This isn't a hack. It's production-ready engineering.
- Rust-powered http-handler crate for zero-copy bridging
- WebAssembly-based binary patcher for Python library loading
- Thread pool management for Python workers
- Full ASGI protocol support
This isn't a hack. It's production-ready engineering.
October 7, 2025 at 3:24 PM
🛠️ The secret sauce:
- Rust-powered http-handler crate for zero-copy bridging
- WebAssembly-based binary patcher for Python library loading
- Thread pool management for Python workers
- Full ASGI protocol support
This isn't a hack. It's production-ready engineering.
- Rust-powered http-handler crate for zero-copy bridging
- WebAssembly-based binary patcher for Python library loading
- Thread pool management for Python workers
- Full ASGI protocol support
This isn't a hack. It's production-ready engineering.
💻 Getting started is simple. Drop your Python app in your public docroot and then:
October 7, 2025 at 3:24 PM
💻 Getting started is simple. Drop your Python app in your public docroot and then:
⚡ Real benchmarks:
- 5,200 req/sec with @platformatic/python
- Beats fastapi run, daphne, and hypercorn
- Sub-2ms latency
- Zero network overhead
Your ML inference just got 10x faster. Your data pipeline? Same story.
- 5,200 req/sec with @platformatic/python
- Beats fastapi run, daphne, and hypercorn
- Sub-2ms latency
- Zero network overhead
Your ML inference just got 10x faster. Your data pipeline? Same story.
October 7, 2025 at 3:24 PM
⚡ Real benchmarks:
- 5,200 req/sec with @platformatic/python
- Beats fastapi run, daphne, and hypercorn
- Sub-2ms latency
- Zero network overhead
Your ML inference just got 10x faster. Your data pipeline? Same story.
- 5,200 req/sec with @platformatic/python
- Beats fastapi run, daphne, and hypercorn
- Sub-2ms latency
- Zero network overhead
Your ML inference just got 10x faster. Your data pipeline? Same story.
Here's the scary truth:
Your app might have hundreds or thousands of npm dependencies.
Each one is a potential attack vector.
And traditional security tools? They're playing catch-up in a game where attackers keep changing the rules.
Your app might have hundreds or thousands of npm dependencies.
Each one is a potential attack vector.
And traditional security tools? They're playing catch-up in a game where attackers keep changing the rules.
October 7, 2025 at 9:48 AM
Here's the scary truth:
Your app might have hundreds or thousands of npm dependencies.
Each one is a potential attack vector.
And traditional security tools? They're playing catch-up in a game where attackers keep changing the rules.
Your app might have hundreds or thousands of npm dependencies.
Each one is a potential attack vector.
And traditional security tools? They're playing catch-up in a game where attackers keep changing the rules.
🚨 The npm ecosystem just got hit with another major supply chain attack.
If your app uses npm packages (spoiler: it does), you must hear this.
We're sitting down with @feross from @SocketSecurity to dissect what happened and how to protect yourself.
Thread 👇
If your app uses npm packages (spoiler: it does), you must hear this.
We're sitting down with @feross from @SocketSecurity to dissect what happened and how to protect yourself.
Thread 👇
October 7, 2025 at 9:48 AM
🚨 The npm ecosystem just got hit with another major supply chain attack.
If your app uses npm packages (spoiler: it does), you must hear this.
We're sitting down with @feross from @SocketSecurity to dissect what happened and how to protect yourself.
Thread 👇
If your app uses npm packages (spoiler: it does), you must hear this.
We're sitting down with @feross from @SocketSecurity to dissect what happened and how to protect yourself.
Thread 👇
🎉 Proud to announce @platformatic.dev is renewing our Open Source Pledge for 2025!
We have committed $12,500+ to support the maintainers and projects that power the Node.js ecosystem.
Because sustainable open source requires more than code—it requires financial backing.
We have committed $12,500+ to support the maintainers and projects that power the Node.js ecosystem.
Because sustainable open source requires more than code—it requires financial backing.
October 6, 2025 at 3:59 PM
🎉 Proud to announce @platformatic.dev is renewing our Open Source Pledge for 2025!
We have committed $12,500+ to support the maintainers and projects that power the Node.js ecosystem.
Because sustainable open source requires more than code—it requires financial backing.
We have committed $12,500+ to support the maintainers and projects that power the Node.js ecosystem.
Because sustainable open source requires more than code—it requires financial backing.
Remember that thread about Node.js + Kubernetes performance issues?
Plot twist: K8s and Node.js are actually a PERFECT match.
The problem? Most teams are using 2010 patterns for 2025 architecture.
On October 1st, we will discuss how to do it right.
Time to level up 🧵
Plot twist: K8s and Node.js are actually a PERFECT match.
The problem? Most teams are using 2010 patterns for 2025 architecture.
On October 1st, we will discuss how to do it right.
Time to level up 🧵
September 29, 2025 at 3:59 PM
Remember that thread about Node.js + Kubernetes performance issues?
Plot twist: K8s and Node.js are actually a PERFECT match.
The problem? Most teams are using 2010 patterns for 2025 architecture.
On October 1st, we will discuss how to do it right.
Time to level up 🧵
Plot twist: K8s and Node.js are actually a PERFECT match.
The problem? Most teams are using 2010 patterns for 2025 architecture.
On October 1st, we will discuss how to do it right.
Time to level up 🧵
Ready to master production Node.js?
Final registration closes soon: ti.to/cityjsconf-l...
See you Monday in London 🚀
Final registration closes soon: ti.to/cityjsconf-l...
See you Monday in London 🚀
September 24, 2025 at 3:59 PM
Ready to master production Node.js?
Final registration closes soon: ti.to/cityjsconf-l...
See you Monday in London 🚀
Final registration closes soon: ti.to/cityjsconf-l...
See you Monday in London 🚀
Five days until my Node.js workshop in London and this is it - final call for seats
If you've been following along for the past 6 weeks, you know this isn't another basic tutorial
This Monday, September 29th, we're diving deep into production Node.js 🧵
If you've been following along for the past 6 weeks, you know this isn't another basic tutorial
This Monday, September 29th, we're diving deep into production Node.js 🧵
September 24, 2025 at 3:59 PM
Five days until my Node.js workshop in London and this is it - final call for seats
If you've been following along for the past 6 weeks, you know this isn't another basic tutorial
This Monday, September 29th, we're diving deep into production Node.js 🧵
If you've been following along for the past 6 weeks, you know this isn't another basic tutorial
This Monday, September 29th, we're diving deep into production Node.js 🧵
🚀 Enterprise Node.js apps are powerful but complex. Over-provisioned clusters, slow autoscaling, and disconnected metrics are silently killing your budget and risking outages.
What if you could predict problems before they happen?
Join us tomorrow, Sep 24th 👇
What if you could predict problems before they happen?
Join us tomorrow, Sep 24th 👇
September 23, 2025 at 4:55 PM
🚀 Enterprise Node.js apps are powerful but complex. Over-provisioned clusters, slow autoscaling, and disconnected metrics are silently killing your budget and risking outages.
What if you could predict problems before they happen?
Join us tomorrow, Sep 24th 👇
What if you could predict problems before they happen?
Join us tomorrow, Sep 24th 👇
Read our launch blog post:
📖 blog.platformatic.dev/the-intelligent-command-center-for-nodejs-is-now-open-source
📖 blog.platformatic.dev/the-intelligent-command-center-for-nodejs-is-now-open-source
September 23, 2025 at 2:59 PM
Read our launch blog post:
📖 blog.platformatic.dev/the-intelligent-command-center-for-nodejs-is-now-open-source
📖 blog.platformatic.dev/the-intelligent-command-center-for-nodejs-is-now-open-source