About the service
I create cloud backends in Java using Quarkus — a framework with which Java finally confidently lives in containers. Instead of heavy servers that need seconds to start and hundreds of megabytes just for idle time, I deliver services that start in tens of milliseconds and hold a tiny amount of memory. This difference is not cosmetic: it is exactly what allows you to scale to zero, bring up replicas at the moment of load arrival, and pay only for actually consumed resources. First, I design the service around your subject area, then carefully connect REST or reactive endpoints, storage, message exchange, and configuration so that the code remains clean as the project grows.
Usually my work covers the entire path from an empty repository to a service running in your cluster. I set up REST endpoints with validation and clear error handling, connect databases through Hibernate with Panache or reactive drivers, add message exchange via Kafka or AMQP when event streams are needed, and expose health checks and metrics so the platform can correctly manage the service. When cold start and memory are truly critical, I build the application into a native GraalVM image: startup is reduced almost to zero, and the container size drops dramatically. Each service leaves with a compact container image, sensible configuration profiles, and a clear surface for the orchestrator.
You get code that is tested, documented, and ready for the pipeline: unit and integration tests, API documentation in OpenAPI format, Dockerfile and clear notes on running and deployment. I care about long-term maintainability, so I keep the structure explicit and avoid tricks that only the author will be able to read later. Whether you need to extract a service from a monolith, start a new product, or bring a Quarkus application that has outgrown its first architecture up to speed, I will bring it from idea to a stable, observable, and production-ready backend.
Usually my work covers the entire path from an empty repository to a service running in your cluster. I set up REST endpoints with validation and clear error handling, connect databases through Hibernate with Panache or reactive drivers, add message exchange via Kafka or AMQP when event streams are needed, and expose health checks and metrics so the platform can correctly manage the service. When cold start and memory are truly critical, I build the application into a native GraalVM image: startup is reduced almost to zero, and the container size drops dramatically. Each service leaves with a compact container image, sensible configuration profiles, and a clear surface for the orchestrator.
You get code that is tested, documented, and ready for the pipeline: unit and integration tests, API documentation in OpenAPI format, Dockerfile and clear notes on running and deployment. I care about long-term maintainability, so I keep the structure explicit and avoid tricks that only the author will be able to read later. Whether you need to extract a service from a monolith, start a new product, or bring a Quarkus application that has outgrown its first architecture up to speed, I will bring it from idea to a stable, observable, and production-ready backend.
