In this article, we are going to look at Microservice architectures, their benefits, what makes them different from traditional monolithic architectures, and how to go about setting up monitoring and alerting for them. MetricFire is a Hosted Graphite, Grafana, and Prometheus service, where we help you set up and manage these open-source tools. If you would like to follow the steps in this blog, make sure to sign up for MetricFire's free trial and even book a demo session.

Microservices and serverless are both important topics in the world of cloud-native computing. Yet, although serverless functions and microservices architectures often go hand-in-hand, they’re distinct technologies that fill different roles in modern software environments. Here’s an overview of what microservices and serverless are, how they relate to each other, how they are different, and why you may or may not wish to deploy a serverless microservice.

When it comes to conversations around application architecture or working with integrations between applications, you’ve likely heard a couple terms pop up a few times: microservice and APIs. You might also have run across the common misconception that microservices are just a way to implement APIs so they can communicate with each other. As you’ll see in this article, there are alternative ways to architect our microservice applications.

With almost every blog you read about monitoring, troubleshooting, or more recently, the observability of modern application stacks, you’ve probably read a statement saying that complexity is growing as a demand for more elasticity increases which makes management of these applications increasingly difficult. This blog will be no exception, but there’s a good reason for that: we just enabled the first Sumo Logic customers with powerful new tools to tackle these exact challenges.

Microservices have changed the way we build applications. Software design has moved from large monolithic applications (which are not really adaptable to changes and improvements) to a collection of small, independent processes infrastructure which is far more suited to adapt to changes in today’s agile world.

In this episode of Coffee & Containers, North American DevOps Group‘s Jim Shilts speaks with Shipa‘s Bruno Andrade and Fiserv‘s Ken Owens. The topics covered include.

At LogicMonitor, we deal primarily with large quantities of time series data. Our backend infrastructure processes billions of metrics, events, and configurations daily. In previous blogs, we discussed our transition from monolith to microservice. We also explained why we chose Quarkus as our microservices framework for our Java-based microservices. In this blog we will cover.

Microservices, also known as microservices architecture, refers to a method of designing and developing software systems. Microservice architecture is becoming increasingly popular as developers create larger and more advanced apps. The goal is to help enterprises become more Agile, especially as they adopt a culture of continuous testing. Here are the basic features of microservices.

The pandemic has accelerated digital business initiatives. Ultimately, it’s the application that delivers new capabilities to customers and employees; but transformation occurs at several layers to support those applications. At VMware, we see our customers navigating three transformations, each of which supports digital business and app modernization at different levels.