I work mainly on the backend, and most of my current stack revolves around building reliable, maintainable systems with Java.
Java is the center of gravity in the way I build software today. Spring Boot is usually my default when I want to move quickly without giving up structure, clarity, or room to grow. A lot of my attention goes into architecture: service boundaries, clean layering, and systems that stay understandable as they get bigger.
Redis is one of the tools I feel most comfortable with, especially for caching, fast lookups, and reducing unnecessary load on core services. For relational data, I usually lean on MySQL. I like stacks that are simple, proven, and easy to reason about in production.
I prefer tools that make systems easier to run, inspect, and evolve. Docker is my default packaging layer, Linux is the environment I trust most, and Nginx is the kind of tool I reach for around routing and deployment edges. I am also interested in Kubernetes as part of building more scalable and operationally mature systems.
I care about shipping software with feedback loops in place. Jenkins, Grafana, and Elasticsearch fit into that way of working: automation, visibility, logs, and a better understanding of how systems behave after they are deployed.
Git and Postman are part of the daily workflow. I also keep an eye on Go and C, partly out of curiosity, and partly because lower-level thinking makes me a better backend engineer.
Right now, the strongest theme in my stack is backend architecture. I’m continuing to deepen my understanding of Java, Spring Boot, system design, and the practical tradeoffs that come with building software meant to last.
