Operations | Monitoring | ITSM | DevOps | Cloud

Cloud

The latest News and Information on Cloud monitoring, security and related technologies.

Observability from Development to Production with Platform.sh Observability

With Platform.sh and Blackfire.io monitor, profile and test your application even before it is released in production. Get actionable insights to improve your code rather than spend time figuring out what’s wrong. Ensure optimal performance and user experience for your web applications.

Differences Between Block Blobs, Append Blobs, and Page Blobs

Azure Blob Storage is a cloud-based storage solution that enables developers to store and manage large amounts of unstructured data. Blob storage can store any type of text or binary data, such as documents, images, audio, and video files. Blobs are divided into three types: block blobs, append blobs, and page blobs. Each type of blob has its unique characteristics and is used for different purposes.

On-prem vs. cloud deployment models: Which option is best?

Is an on-premises or cloud infrastructure better for your business? It depends. Here’s how to make an informed decision. In the world of technology, there is often a tendency to fall into the trap of “shiny object syndrome” — when we assume newer must mean better. But if that’s the case for cloud environments, could it spell the end of on-premises infrastructures? Cloud computing adoption has become synonymous with modernizing IT infrastructures.

Understanding Azure Blob Storage Metadata: A Complete Guide

In today’s world, data is king. Companies and organizations are generating vast amounts of data every day, and they need a way to store, manage, and organize that data. This is where cloud storage solutions like Azure Blob Storage come into play. Azure Blob Storage is a scalable, secure, and cost-effective cloud storage solution that allows you to store and retrieve large amounts of unstructured data. One of the key features of Azure Blob Storage is metadata.

Epinio Meets s3gw

Since the very first version, Epinio has made use of an internal S3 endpoint to store the user’s projects in the form of aggregated tarballs. Those objects are then downloaded and staged by the internal engine’s pipeline and, finally, they are deployed into the Kubernetes cluster as consumable applications. Epinio makes use of S3 as an internal private service. In this scenario, S3 can be thought of as an internal ephemeral cache with the purpose of storing temporary objects.