About the service
I develop reactive, event-driven backends on the JVM using Eclipse Vert.x and design them from the first line to remain non-blocking under real load. Everything is built on event loop: I keep blocking work out of the event cycle, heavy operations I move to worker verticles or executeBlocking, and I build the request path so that one thread serves thousands of simultaneous connections without delays. I watch the details that decide throughput at scale: back-pressure on streams, connection pools, sensible timeouts, and careful failure handling instead of silent retries that only make the incident worse.
On Vert.x I built real-time and high-concurrency systems: streaming APIs, WebSocket gateways, message brokers, IoT data ingestion, and platforms that distribute work across a cluster. I rely on event bus for loose coupling, reactive streams for controlled data flow, and clustering when one node is not enough. You get not just code: a documented architecture, meaningful tests, including load tests, metrics and tracing so the system is transparent in battle. I can launch a project from scratch, rescue floundering reactive code, or gradually move an application from a "thread per request" model to an event-driven architecture.
Most often I take tasks like this:
— Real-time APIs, WebSocket and SSE gateways
— Data ingestion and streaming under high concurrency
— Cluster services on event bus with back-pressure
— Performance tuning and migration from blocking stacks
On Vert.x I built real-time and high-concurrency systems: streaming APIs, WebSocket gateways, message brokers, IoT data ingestion, and platforms that distribute work across a cluster. I rely on event bus for loose coupling, reactive streams for controlled data flow, and clustering when one node is not enough. You get not just code: a documented architecture, meaningful tests, including load tests, metrics and tracing so the system is transparent in battle. I can launch a project from scratch, rescue floundering reactive code, or gradually move an application from a "thread per request" model to an event-driven architecture.
Most often I take tasks like this:
— Real-time APIs, WebSocket and SSE gateways
— Data ingestion and streaming under high concurrency
— Cluster services on event bus with back-pressure
— Performance tuning and migration from blocking stacks
