Carlo Maria Cardì · Backend engineer

Backend software.Clear decisions.Fewer surprises.

I build backend systems, security tools and infrastructure with one practical goal: keeping their behaviour understandable when the pressure rises.

See selected work Let’s talk

Open to selected collaborationsCatania, Sicily

Right now

BuildingShardify

StudyingComputer Science · UniCT

Working inJava · APIs · Data

Based inCatania · Europe/Rome

01 · Selected work

Software with a reason to exist.

Three projects shaped by real constraints: less coupling in the data layer, better security decisions and honest load testing.

Shardify

A persistence library for Java 23+ that gives SQL and NoSQL stores one coherent interface, with multi-level caching and reactive support.

The point

Reduce infrastructure coupling without pretending that every database behaves the same.

Axiom AntiVPN

A VPN and proxy detection API for fraud prevention, fast decisions and resilient production use.

The point

Turn noisy network signals into a risk decision a product can use at the edge.

Minecraft Bot Stress Tester

A Node.js and Mineflayer harness that simulates concurrent clients, movement and chunk loading through a practical web interface.

The point

Make a server’s limits visible before real players are the ones who find them.

02 · Expertise

Backend work, from first boundary to production.

Architecture matters. So do failure modes, deployment paths and the person debugging at two in the morning.

Service architecture

Clear boundaries, durable contracts and data flows that can evolve without turning every change into a migration crisis.

REST · gRPC · Events · Queues

Performance engineering

Profiling before guessing. Caching, indexing and concurrency choices tied to measured bottlenecks.

JVM · Redis · PostgreSQL · Load tests

Application security

Threat-aware APIs, practical vulnerability analysis and hardening built into delivery from the start.

OWASP · Pentesting · Network hardening

Production delivery

Containers, repeatable releases and useful telemetry that help explain incidents instead of decorating dashboards.

Docker · Linux · Nginx · Cloudflare

03 · Method

A small set of rules, used consistently.

“The best backend is not the one with the most moving parts. It is the one whose behaviour stays legible under stress.”

I study Computer Science at the University of Catania and build software through Axiom Enterprise. Theory and production stay close: define the constraints, test the assumptions, then instrument what remains.

01Make failure explicit

02Measure before optimising

03Secure the boundary

04Leave the system easier to operate

04 · Working stack

Tools are choices, not an identity.

I choose them around the system’s constraints and the team that will maintain it.

01Languages

JavaKotlinTypeScriptPythonGoC

02Backend

Spring BootNode.jsgRPCRESTWebSocketsRabbitMQNATS

03Data

PostgreSQLMongoDBMariaDBCassandraRedis

04Platform

DockerKubernetesNginxLinuxCloudflareCI/CD

05 · Contact

Have a backend problem worth untangling?

Send the context, constraints and timeline. I’ll reply with a concrete next step—whether or not I’m the right person for the work.

Write an email