DEV Community

David Brewer
David Brewer

Posted on


What do you do if a microservice in your ecosystem goes down?

At least once a month I find myself in a moment where multiple servers, or a single point of failure server, is down. I worked back-end for years but now that I work on front-end products in a React project space, I really notice this issue more and would love to find a solution for this.

If a server in your microservice ecosystem is down, what do you do? Every time it happens I think of running the back-end projects locally to keep working, but when you have a large set of servers to run, its very complex to get every project running.

Top comments (1)

rslak profile image

Build observability to your micro services and that way you will know the reasons why it was down. It is basically setting up logging, metrics and alerts in your codebase and deployment. If it is cloud based deployment, there are services that are prebuilt and ready for use like azure app insights. If you have on premise deployment, then you can rely on custom logging and OSS telemetry products

Top Posts from the React Ecosystem

1. Changes In The Official React Documentation

The former React Docs Beta has been officially released as the updated React documentation at after years of hard work and refinement. Check out the brand new React Docs: What’s New in the Updated React Docs

2. CRA's Time is Over

React developer team has removed create-react-app (CRA) from official documentation rendering it no longer the default setup method for new projects. The bulky setup, slow, and outdated nature of CRA led to its removal: create-react-app is officially dead

3. How to Fetch Articles for Your Portfolio

Integrate the articles of your profile into your personal portfolio with either React, Vue, or Next.js by following these simple steps. It outlines how to include frontend to pull the information and correctly utilizes the API: How to Fetch Your Articles for Your Portfolio with React