Technologies I work with
From enterprise Java backends to modern frontends and cloud infrastructure. Below you can click through a typical application and see what each layer does.
What I actually use
Not a list of everything I have ever come across — only the technologies I genuinely work with on production projects.
How an application fits together
Click any layer and I will explain what happens there and which technologies I use.
Frontend
The screen the user actually sees. I build it in Angular or React, and for smaller sites in plain HTML, CSS and JavaScript — no framework slowing the page down.
API layer
The interface systems talk through. I write REST and SOAP services against XSD and WSDL contracts, documented in OpenAPI so they can be relied on.
Microservices
The application logic split into separate services. Each does one thing, deploys on its own, and if one falls over the rest keeps running.
Message queue
When something happens, the system does not have to handle it right away. Events travel through a queue, so a traffic spike floors nobody and nothing is lost.
Data layer
Where the data actually lives. Relational databases for things that must add up exactly, document stores for flexible content, Elastic for fast search.
Cloud and deployment
The application packaged into a container and deployed automatically through GitLab CI to AWS, Azure or OpenShift. Deployment is as boring as it should be.
The same approach applies to smaller jobs — custom website development and mobile app development rest on the same foundations.