Honeycomb uses AWS Lambda as a core part of our query execution architecture; Lambda’s ability to quickly allocate lots of resources and charge us only for use is invaluable to keeping Honeycomb fast and affordable. Our total Lambda bill is easily accessible in the AWS Console, but how do we know which customers or application areas dominate this bill? How do we judge the cost of changes we make to our own software?
Monitoring performance in front-end applications is vital. It focuses on the areas of the application users experience. These areas are slow rendering or frame rate, network request errors, and unresponsive user experience. Your application’s users expect the experience of using the application to be fast, responsive, and smooth. In the first article of this series, we discussed some tips for optimizing your React Native application performance.
In a world where the customer’s digital experience is critical to business outcomes, it is crucial to understand how our applications are behaving. As businesses increasingly rely on the performance and availability of revenue-generating applications, the tolerance for downtime and slow response times has plummeted – so the response to production issues must be quick and effective.
So here we are…the final chapter. In Part 2 of this series, we started to drill down into some of the concepts that make Kafka great. We concluded that although terminology between MQTT and Kafka was similar (for example topics), they behaved quite differently under the hood. We also took a brief overview of Kafka Connect and how we can use some of the enterprise connectors to stream our data to other platforms. Yet we did learn that Kafka does have some shortfalls.
Morph is a new database migration tool designed to improve Mattermost schema migrations. It can be used programmatically with a library and from a CLI. Morph stores the schema version in a table, where all applied migrations are persisted. It’s a flexible open source library that can be used with a driver interface implementation and a source to read migration scripts from. The engine uses a dependency injection pattern so that any implementation can be used with the library.
Frontend monitoring is a process of tracking and maintaining the health of an application’s client-side. It involves monitoring the availability, functionality, and performance of the client-side of an application. We can segment a web application into two parts. I.e., client-side and server-side.
If there’s one essential thing we’ve learned from being in the business of digital operations for more than 13 years, it’s that every business has a unique approach to building resilience with its bespoke tech stacks and processes. Many PagerDuty customers around the world are starting to provide direct access to their on-call teams with Live Call Routing (LCR).
