opentelemetry-ext-js VS sqs-consumer

AWS has good tools for tracing, but in this example, I will use another remote and distributed tracing platform – Aspecto.

For this article, I will be using Aspecto to visualize my traces. You can follow along by quickly creating a free account.

If we drill down into one of these traces, we can see in more detail how long each request took and clear visualization of the entire workflow.

For the purposes of this guide, I chose to use Aspecto as my visualization tool. This is because Aspecto provides built-in support for visualizing messaging systems like Kafka (and, of course, any other part of our microservice architectures).

To follow along, you can open a new free-forever Aspecto account or log in to your existing one.

That’s about it for this OpenTelemetry Java guide, folks. If you have any questions or issues with any of these steps, feel free to reach out to us via chat or join our OpenTelemetry Slack channel (part of the CNCF Slack).

At Aspecto, you can sign up for free and use our generous free-forever plan (no limited features).

Aspecto has a free-forever tier and provides everything included in Jaeger and more. Sort of like Jaeger on steroids.

However, you can take your tracing visualization to the next level with Aspecto. Try it yourself with the free-forever plan that has no limited features.

Hi all, we wanted to share some love back to the Kafka community. We hope you'd find this instrumentation helpful, check it out on GitHub 🌟and npm

You could utilize a wrapper like sqs-consumer. Check out their implementation.

To receive the messages from the queue, we will use the sqs-consumer library. The service will receive messages describing newly created orders. After some processing, it will change the order status in the table to ‘completed’.

As we built out this new system, we looked at the current module ecosystem to determine if anything would fit our needs to keep this queue cleared. Unfortunately, the best module we could find, sqs-consumer, did not support FIFO queues and the issues indicated they did not have any intention to do so. Therefore, we wrote sqsiphon. Our library heavily borrows from the public interface of sqs-consumer, but is implemented in a much different way. In particular, sqsiphon leverages the Node.js event loop through setImmediate to build the polling mechanism instead of relying on SQS's "long polling" feature. Additionally, sqsiphon utilizes the JavaScript prototype to reduce reliance on expensive closures. As a bonus, OpenTracing support is built-in to sqsiphon so that applications built with it can be monitored effectively. The result is a library that can poll SQS extremely quickly while requiring very little overhead.