The focus of the latest Hawkular APM release
has been in building a compatibility layer for ZipKin-aware applications. In this blog post, we’ll show how Hawkular APM can
be used as a drop-in replacement for ZipKin server and UI.
A video demonstrating this approach can also be viewed here.
At the end of this blog post, we should see data flowing from the target applications to Hawkular APM, without any code changes
to the application themselves:
Red Hat offers a Container Developer Toolkit, or CDK, for its customers,
allowing for a quick start on developing applications following the best practices on the microservices architecture.
Along with the CDK, Red Hat publishes also a "MSA - Hello World Microservices Architecture",
which demonstrates how applications might benefit from this architecture. It can also be used as seed for your own
projects, as it shows how activities can be accomplished by using several technology stacks, from nodejs/express
to Wildfly Swarm
.
For Hawkular APM, this offers a great way to test our APIs on different stacks, specially our ZipKin compatibility layer. Ideally,
one would simply point the ZipKin URL setting to a Hawkular APM server and everything would just work.
And that’s what we are going to do in this post!