In this article, we will walk through common ways of implementing authentication microservices.  We will have 2 parts:  1. The theoretical part talking about OpenID Connect, OAuth 2.0, JWT, etc.

In this article, you’ll learn how to run Jaeger locally, why and when you should do it, as well as what are Jaeger’s limitations when running locally. Let’s start with

Originally published on The New Stack. When debugging microservices, it can be challenging for developers to identify the root cause of issues. Not to mention how frustrating it is to

Today we released a first-of-its-kind OpenTelemetry auto instrumentation plugin. An OpenTelemetry Socket.io Instrumentation for Node.js. What makes this instrumentation different? Well, first, it’s the first full instrumentation for Socket.io ever

TL;DR – A step-by-step tutorial video + a GitHub demo repo are below. When it comes to complex microservices architecture, using messaging brokers is a no-brainer. Communicating over a message

Microservice applications grow in complexity as the number of services grows.  This is something I’ve seen time and again as I’ve worked in microservice-based application architectures – one minor change

Microservice applications rely heavily on messaging and asynchronous communications to keep everything working smoothly.  Choosing the right message broker is one of the first critical choices you must make when

In this post, I will walk you through how to use Lerna to manage, and publish, two packages under the same monorepo. Publishing will be done to my private GitHub

Microservices have tons of benefits.  They enable distributed development of highly scalable applications and unleashing the full potential of public cloud infrastructure. But there can be no good without evil.

I recently worked on an npm package that is supposed to be consumed on both Node.js environment and the browser (using React/Angular/etc..). Things started getting complicated when the node branch