With the growing adoption of remote and distributed application development including micro-services, cloud-native applications, serverless, and more, it is becoming challenging more than ever before for developers to troubleshoot issues within a reasonable time, and that is a bottleneck. That in a sense contradicts the objectives of Agile and DevOps through fast feedback loops, continuous delivery, quick MTTR (mean time to resolution of defects), etc.
The foundation of software development is rooted in the handling and preservation of data in compliance with the goals of the application. The core of any software program is the information stored in databases that is used for retrieval and manipulation. To ensure that the chosen database system (whether SQL or Non-SQL) is suitable for the needs of the application, it’s important to conduct tests to evaluate its capabilities.
Managing your own time series database is painful. We’ve moved from servers to services, and yet, monitoring metrics data is primitive. Our managed time series database powers mission-critical workloads for monitoring, at a fraction of the cost.
This is just a quick blog to draw attention to some new and enhanced monitoring dashboards we have added to eG Enterprise in the upcoming release (v 7.2) to provide quick and powerful overviews of a range of AWS services. As with all our dashboards, color-coded overlays provide guided drilldown for help desk operators and administrators. If a component has an issue, an amber or red indicator is overlaid to allow the viewer to click through to further diagnostic information.
In a previous post, I explained how we made our Ubuntu image 15 times smaller by chiselling a specific slice of Ubuntu for.NET developers. In this blog, I will provide step-by-step instructions on customising your chiselled Ubuntu base images for any use case. I don’t believe in a perfect container base image anymore.
