Design Patterns in the Cloud – Monitoring

Design Patterns in the Cloud Menu

The cloud design patterns on monitoring are related to the patterns used for applications to be monitored in cloud environments, since availability, incidents, errors, or problem management can be cumbersome and difficult in complex or scalable cloud environments, and where you don’t have full control of the infrastructure and must be able to allow external tools or monitoring to detect problems and availability of the same and its components. The patterns are as follows:

Health or status monitoring access point pattern (Patrón de Punto de acceso de monitoreo de estado o salud)

This pattern is the way to expose in our applications entry points to expose system status information so that external tools, other applications or queries can access or receive information on the status of the system components. For example, it’s very common to have services or applications that every certain period of time, run a checklist to corroborate the status of an application, system or service. These components must have some entry point where these other tools or programs can consult these validations, whether it is the status of the database, of a service, of a server, of a connection, of a permission, etc.
The most popular platforms provide their own tools in the monitoring consoles to query information from our applications or even using some SDK or components within the application we can easily send notifications or status to these tools.

Sidecar Pattern (Patrón sidecar)

This pattern that is ussually used in the cloud for many other things (usually for decoupling), in this case serves to isolate tools or system components for self-monitoring.
The most common example is logging tools and components.
In this case, our applications must have or allow interfaces with external tools or systems to output information from the application, but not the application to have the responsibility to do so.
As the previous pattern, there are tools in all the most popular platforms to implement it. Tools for logging, transactions, requests, hardware component peaks, etc.
For this pattern it’s essential that our applications are adapted to connect to any external monitoring tool.

Design Patterns in the Cloud Menu

About the author:

Matías Creimerman

I’m a specialist in design, development and management of software solutions with almost 20 years of experience. Microsoft Certificated Professional (MCP). Expert in dot net and Microsoft technologies. Experience and skills in designing solutions in a wide range of commercial, industrial and production areas. Design of architectures, software applications and processes. Skills in leadership and team management. Tech trainer. Technology researcher. Self-taught and dedicated to continuous learning. Skills in estimation, quotation, projects proposals and solutions design. Entrepreneurial spirit. Strong Tech profile but also customer oriented. I perform roles as fullstack dev, tech consultant, technical referent, development leader, team leader, architect, cross leader, tech manager, tech director, trainer, ramp-up & follow-up teams, software factory manager, DevOps and release manager. Regular chess player and musician.

Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License

This content is property of Matias Creimerman Any misuse of this material will be punishable This work is licensed under a International Copyright Law protects «original works of authorship» including photographs, videos, and blog posts posted on social media sites The content has no rights to be shared without authorization or citation to the author. This content cannot be sold be adapted or modified partially or totally. All content shared outside this blog that doesn’t belong to the author must have citations to the author.