Filippo De Luca
I build backend systems the way I was taught to build engines first: understand every tolerance before you trust the assembly. These days that means Scala, Cats Effect and event-driven architectures — not pistons — but the discipline carried over.
Role
Technical Lead (contract), SiriusXM — User Services / Device team
Stack
Scala, Cats Effect, AWS (Lambda, DynamoDB, Kinesis, CDK)
Prior work
Kaluza / OVO Energy — designed a GraphQL-over-Kafka API architecture
Origin
Trained as a mechanical technician (perito meccanico) before software
Based in
Rome, Italy — working remotely
Available for
Contract and freelance work — backend, event-driven and distributed systems
Latest posts
22 Sept 2026 · 8 min Exactly-once is a memory problem
You will receive the same message twice. The fix isn't a stronger delivery guarantee — it's remembering what you already did, and one database primitive is enough to do it.
08 Sept 2026 · 6 min Splitting events by type breaks the only ordering you had Three ways to lay out domain events across Kafka topics. One of them looks like the tidy option and quietly costs you the ability to rebuild state at all.
28 Aug 2026 · 5 min How a cat can quack Duck typing says: if it quacks, it's a duck. Type classes say something stranger and more useful — it is not a duck, it never was, and you taught it to quack anyway.
10 May 2023 · 4 min Harnessing the power of Avro and the Schema Registry Why Avro is worth the extra moving parts on Kafka, what the five bytes in front of every message are for, and how the serializer and the schema registry keep incompatible data off your topics.