Whenever I look broadly at my career in telecom, one area that always amuses me is the extent to which our collective business enjoys its peculiarities. Sort of like our own secret handshake society full of unique terms and abbreviations like AIN & ANI, DDI and CLID or CLECs and POTS. After all, the Bell System used to formally publish a list of abbreviations and acronyms. Maybe it is just in our DNA?

Azure Event Hubs are cloud-scale telemetry ingestion from websites, apps, and devices. Because of the tremendous event handling capacities, IoT architectures also consume the Azure Event Hubs. Thus, we talk about handling millions of events per second. With the implementation of multiple partition architecture behind the scenes, Azure Event Hubs are highly scalable to receive events from hundreds of sources.

Putting it simply, it is how you do DevOps in Git. You store and manage your deployments using Git repositories as the version control system for tracking changes in your applications or, as everyone likes to say, “Git as a single source of truth.”

What if I told you that a text file could help you tackle the normally tedious and time-consuming task of setting up and managing your AWS infrastructure? Good news. It’s actually easy to do with an AWS CloudFormation template. A typical AWS infrastructure can consist of numerous resources that might need to be managed across different accounts and regions. Setup is often a manual process that can be overwhelming to maintain.

Monitoring systems help DevOps teams detect and solve performance issues faster. With Docker and Kubernetes steadily on the rise, it’s important to get container monitoring and log management right from the start. This is no easy feat. Monitoring Docker containers is very complex. Developing a strategy and building an appropriate monitoring system is not simple at all.

Applications fail. Containers crash. It’s a fact of life that SRE and DevOps teams know all too well. To help navigate life’s hiccups, we’ve previously shared how to debug applications running on Google Kubernetes Engine (GKE). We’ve also updated the GKE dashboard with new easier-to-use troubleshooting flows. Today, we go one step further and show you how you can use these flows to quickly find and resolve issues in your applications and infrastructure.

People sometimes think that implementing Site Reliability Engineering (or DevOps for that matter) will magically make everything better. Just sprinkle a little bit of SRE fairy dust on your organization and your services will be more reliable, more profitable, and your IT, product and engineering teams will be happy. It’s easy to see why people think this way. Some of the world’s most reliable and scalable services run with the help of an SRE team, Google being the prime example.

2020 was indeed challenging for Kovai.co still had great learning! One of them is what I am sharing with the community through this blog. For enterprises like us, worldwide work from anywhere became the new reality. We had to move towards a cloud-native world where secure data storage and effective remote management of IT infrastructure were of supreme importance.

It’s no secret that AWS bills are confusing. But it’s particularly difficult for the team who actually writes the check to Amazon for hundreds of thousands or millions of dollars — yet has never personally seen what the inside of the AWS portal looks like (and probably never will).

Software deployment tools allow developers to ensure that software is properly installed with it’s required packages and implementation steps conducted in the correct order. Using these tools is a vital requirement for any business that creates its own software in-house. There is a variety of software that can assist developers in launching their latest code with new ones (such as GitHub Actions) arriving to the forefront of many growing consideration lists.