Operations | Monitoring | ITSM | DevOps | Cloud

These days, organizations of all types, sizes and industries are using the cloud for a wide variety of business reasons and use cases. Benefits include agility, elasticity, cost savings, ease of deployment, ease of management, ease of procurement and ability to leverage cutting edge technologies. JFrog customers are no different. Indeed, JFrog recognizes that many customers want a hybrid cloud approach with the ability to work across multi-clouds.

Today, automation and configuration management tools are critical for operation teams in IT. Infrastructure as Code (IaC) is the way to go for both Kubernetes and more traditional infrastructure. IaC mixes the great capabilities of these tools with the excellent control and flexibility that git offers to developers.

Microservice architecture is an application system design pattern in which an entire business application is composed of individual functional scoped services, which can scale on demand. Each team focuses on an individual service and builds it according to their skillset or language of choice. In addition to flexibility, this pattern provides: These features have made microservices architecture a popular choice for enterprises.

Resolving the incident is only half the battle when it comes to responding to incidents. For many teams, incident communication is an afterthought, leaving stakeholders inside and outside the organization guessing what happened. But ensuring that important information about the incident is disseminated clearly and quickly is essential.

This is the second blog in a series focusing on how telecom operators can leverage public clouds to meet their business demands. In a previous blog, we talked about Amazon Web Services (AWS) and how its services made it possible for telcos to shift towards public clouds. In this blog, you’ll get to know about Google Cloud Platform (GCP) and its role in enabling the telecommunications industry to leverage the cloud’s capabilities.

I am excited to launch a new series of engineering articles to dig into all the details of How we Built Qovery. A platform built for DevOps, SRE, Platform Engineers, and Developers since January 2020. Since day 1, the Qovery team has strived to make Qovery as open as possible and fight against the black box effect! In this series of 5 articles, I will explain as much as possible how things work behind the scene.

OpenTelemetry is an open-source project under the Cloud Native Computing Foundation(CNCF) that aims to standardize the generation and collection of telemetry data. The telemetry data helps developer, DevOps and IT teams to keep a check on their application health. The telemetry data collected by OpenTelemetry consist of logs, metrics, and traces. Together, they are used for performance monitoring and observability in distributed systems. At SigNoz, we are building an OpenTelemetry native APM.