Epsagon's Browser Tracing: Correlate Frontend and Backend Microservices

Monitoring digital user experiences is a critical part of an observability solution. Understanding the reason for a poor visitor experience on your website or analyzing the health and performance of your website can help fix issues quickly so that they don’t impact a significant user base. That is why we have integrated Browser Tracing into our solution. Browser Tracing can be considered as a part of Real User Monitoring.


Microservices vs Web Services

The differences between microservices and web services deal with different concepts in modern application design. A microservice is a small, independent, application that performs a highly focused service as well as possible. A web service is an internet-based interface that makes the “services” of one application available to applications running on different platforms.


Reducing microservice overhead with shared libraries

It’s a common story: the product team gets early success and grows into a large monolithic code base. While everything is in a single code base, features can be added quickly. This is partly due to the ability to leverage shared code across each feature in the codebase. When your team is adding a new feature, a developer can leverage the existing codebase for needs such as logging or special error handling.


Data Hiding and Microservices: Information Management That Supports Independent Deployment and Teams

A significant part of breaking a monolithic application into microservices involves a redesign of how the application manages data — usually through a data management strategy called “information hiding.” In this respect, breaking a monolith into microservices isn’t just about establishing clear separations between the code for different services. It’s also about creating clear separations between the data that each microservice interacts with. Why information hiding?


Tutorial: Set Up Event Streams in CloudWatch

When building a microservices system, configuring events to trigger additional logic using an event stream is highly valuable. One common use case is receiving notifications when errors are seen in one of your APIs. Ideally, when errors occur at a specific rate or frequency, you want your system to detect that and send your DevOps team a notification. Since AWS APIs often use stateless functions like Lambdas, you need to include a tracking mechanism to send these notifications manually.


SOA vs. Microservices

Most individuals who work in technology — and in particular, cloud computing — are likely aware of how service-oriented architecture (SOA) and microservices work. There is much discussion, however, regarding the best approaches for various situations. There are crucial differences in data governance, component sharing, and the architecture between SOA vs. microservices. In this article, you'll learn the basics of SOA vs.


Security Game Plan for Your Microservices Applications

The demand for digital transformation has accelerated, with 62% of technology leaders sharing that they fear they are at risk of being displaced by competitors who innovate more quickly. Enterprises are increasingly transitioning from monolithic to microservices architecture, with the goal to accelerate application development, speed up innovation and reduce time to market.


Event-driven autoscaling in Kubernetes

In modern cloud architecture applications are broken down into independent building blocks usually as microservices. These microservices allow teams to be more agile and deploy faster. Microservices form distributed systems in which communication between them is critical in order to create the unified system. A good practice for such communication is to implement an event-driven architecture.

From Native Microservices to Full API Gateway Adoption in a Hybrid Mesh Ecosystem in the Cloud

ManoMano is a french DIY marketplace that faces scalability issues due to its hyper-growth — 100% growth in 2020 to €1.2 billion. To tackle this challenge, their website has slowly transformed from a “classic” backend application serving html to a microservices-based architecture.