blog cover opentracing jaeger

What (the hell) was my app doing: First steps with Opentracing and Jaeger

Try to Google a bit and find some blog posts about adoption of microservices, Docker, Kubernetes and other “new” stuff in the traditional environments. Almost every post is like “yeah, microservices are kinda cool, but monitoring and overall observability is very challenging.”

Well, that’s not true anymore. And today I’m gonna show you one important pillar of this shift from “challenging” to “absolutely possible.” Please make some noise for the technology which can’t be missing in your microservice stack – distributed tracing.

Štěpán Vraný

Štěpán Vraný

DevOps Engineer

Micro services in the agency development?

As you might know from our previous blogs, our primary language for writing backends is Node.js. One of the main reasons why we have chosen this technology was that we started to feel the limits of all the other classic monolithic applications, where all the basic logics, renders, request processing and so on were done in one codebase. It was rather limiting not only technologically, but also from the human resources point of view. Also in the area of our PHP “ends”, according to our recently finished projects, we used to divide the final depicting layers into the individual thin client written in React. But we wanted to go even further; dividing the backend into multiple smaller and self-maintaining parts.



Dominik Veselý

Software Analyst & Architect