Operations | Monitoring | ITSM | DevOps | Cloud

Open-source software (OSS) relational database management systems (RDBMSes) are becoming incredibly popular in the cloud computing world. In this article, I’ll discuss one of the most popular OSS relational databases, PostgreSQL, and the options you have for this database in the Microsoft Azure cloud. It’s worth noting these products are large with many detailed aspects, so consider this article a cursory, high-level overview of each offering.

Let’s imagine, for a moment, that we live in a perfect world. In that world, you could check your company’s cloud bills and financial reports and find cleanly organized categories of spending that help you instantly understand where your money is going and why. Your engineers would meticulously label every spend item with useful metadata tags so you can clearly see which costs have increased and which are most affecting your bottom line.

Testing is a vital part of the mobile app development process. Your team can use testing to evaluate the quality, security, and reliability of mobile apps before releasing them to your users. Users who expect their applications to be highly performant and intuitive. There are two ways DevOps teams can perform testing for mobile apps: on-premise (also called self-hosted) or in the cloud. But which of these is the best option for your team?

Cloud migration efforts continue to grow today as organizations move into a post-pandemic work environment. According to McKinsey & Company, by 2024, most enterprises aspire to have $8 out of every $10 for IT hosting go toward the cloud. In a survey by Morgan Stanley, CIOs say cloud computing will see the highest rate of IT spending growth in 2022.

Businesses today know what a cloud migration brings to the table regarding growth and optimization. AWS is the most popular cloud platform for hosting applications of varying complexity. But, with businesses aiming to upscale faster, the deployments tend to become difficult to track. This is one of the many reasons businesses need AWS monitoring tools. This blog will discuss the industry’s best practices for AWS monitoring.

When you build a cloud-based application, you can choose to deploy the resources using the GUI (Graphical User Interface) or CLI (Command Line Interface) provided by the cloud provider. This approach can work well with just a handful of resources, but as the complexity of your application increases, it can become difficult to manage the infrastructure manually.

You've heard of Amazon, but do you have any idea how many services they actually offer? They have their online store, streaming video service, Audible for audiobooks, AWS for commercial cloud computing and server services, and so very much more. Did you know they have a cloud photo service called Amazon Photos? Well, they do. Is Amazon Photos good enough to try out, and can you trust such a massive cooperation with all of your precious photos?

Serverless technologies let us do more with less effort, time and energy. They let us focus on creating user value and let the cloud handle undifferentiated heavy-lifting like scaling and securing the underlying infrastructure that runs our code. Serverless technologies have allowed me to accomplish tasks as a solo engineer that used to take a whole team of engineers to accomplish, and I’m able to complete these tasks in a fraction of the time and cost to my customers.

Does your development team want to snooze alerts during non-business hours? Or proactively prevent the creation of expected alerts for an upcoming expected maintenance window? Cloud Alerting in Google's Cloud operations suite now supports the ability to snooze alert policies for a given period of time. You can create a Snooze by providing specific alert policies and a time period. During this window, if the alert policy is violated, no incidents or notifications are created.

Picking the right AWS instance is challenging because you have to match the ever-changing resource usage patterns of your apps with the 500+ AWS instance types, and the result is over-provisioning and waste. Nearly one-third of businesses exceed their cloud budgets by as much as 40%, in part due to poorly sized instances.