Operations | Monitoring | ITSM | DevOps | Cloud

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?

One question we frequently hear from customers using the Microsoft stack is, “should I use Git or TFS?” The question requires a little decoding due to the way that Microsoft has shifted their brands over time. Here’s some background. Many people still refer to this as “TFS,” regardless of the version they are using. TFVC used to be the default type of repo for TFS projects.

First of all what is appfleet? appfleet is an edge compute platform that allows people to deploy their web applications globally. Instead of running your code in a single centralized location you can now run it everywhere, at the same time. In simpler terms appfleet is a next-gen CDN, instead of being limited to only serving static content closer to your users you can now do the same thing for your whole codebase. Run the whole thing where just your cache used to be.

Snapshots in Azure is a nice feature that allows you to take a read-only, “point in time” snapshot of a Virtual Machine’s disk. You can take a snapshot of a VM’s OS or data disk. You can use this snapshot to revert the VM to a point in time before an event occurred, or you installed something that didn’t go quite right.

"The future-ready enterprise can only be understood as an ecosystem of interdependent components." In our latest webinar, Applied Futurist Tom Cheesewright and Console Connect’s Neil Templeton dug deeper into the findings of our ‘Building Tomorrow’s Interconnected Enterprise’ report, and highlighted how rapid technological change is disrupting traditional business models.

Companies worldwide these days make use of DevOps with a view to attain better profit and progress. Despite its increased use, DevOps can lead to higher risks if not properly handled. There should be an integration of security and development process form the beginning in order to have a risk-free progress. The entire organization will be at risk if proper security check is not practiced in each stage, as cyberattacks are increasing each day.

Virtualisation plays a huge role in almost all of today’s fastest-growing software-based industries. It is the foundation for most cloud computing, the go-to methodology for cross-platform development, and has made its way all the way to ‘the edge’; the eponymous IoT. This article is the first in a series where we explain what virtualisation is and how it works. Here, we start with the broad strokes.

Security in software is now everyone’s problem. We can no longer simply rely on InfoSec teams or your equivalent Gary “he-likes-security” to handle security-related processes and issues. All software, tools, infrastructure, and services need to be trusted. It is important to us at Cloudsmith to provide you with the ability to build that trust within your teams or with your customers. Cloudsmith allows you to use your own domain name for your repositories.

Starting out with runbooks can be daunting, we've built a way to implement our best practices into a runbook that can be implemented in a single click. On top of this, there's now even more ways to attach runbooks to your incidents and a much easier way to test out the runbook that you're currently working on.