Menu

Debugging a distributed mystery
πŸ“°

Debugging a distributed mystery

DEV Community: microservicesΒ·Odinaka Robert NnamaniΒ·1 day ago
#luEoQLdg
#devtomicroservices#devto#dev#user#service
Reading 0:00
15s threshold

In a monolith, a bug lives in one place. You open the logs, you find it.

Microservices change the problem. A single user action can cross 5+ services β€” and the failure can sit in any one of them, or in the gap between two of them.

Take a signup:

Auth service β†’ User service β†’ Notification service β†’ Email provider

Say it fails halfway. The user exists, but the welcome never arrives. Or the account never gets created, but the notification already went out. Where do you look?

Without centralised logging and tracing, you open four dashboards, four log files, four different formats β€” and you guess. Each team can honestly say "it worked on my side," because each side only saw its own hop.

The fix is not more logs.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.