Recently I made a career switch and with that, here I am back to learning the alphabets! I mainly come from a software/application background and the new role I’ve landed myself into requires of me not only the application knowledge but also the relevant hardware understanding. What that means for me is going back to
In the previous part we talked about clusters and the core concepts associated with them. We talked about what they are, how they work, how to create them, register them and manage them end-to-end via Windows Admin Center (WAC). In this chapter we are going to talk briefly about some networking concepts associated with Azure
When you deploy Azure Stack HCI, you deploy it in the form of a cluster, with multiple nodes participating. A cluster is basically a group of otherwise independent servers (nodes) that are interconnected to work with each other to provide features like scalability, high availability, load balancing, etc. and many more. An HCI cluster collects
In the previous part we talked about Azure Arc, which is integral in our Azure Hybrid Cloud story. Azure Arc is essentially the glue that sticks our on-prem or multi-cloud infrastructure to the Azure portal, for unified management and control. We are now ready to move on to other infrastructure focused concepts such as storage,
In the previous part we discussed the “HCI” part in Azure Stack HCI and how it is different than the conventional non-converged infrastructure and the advantages of it. Azure Stack HCI is very tightly coupled with Azure Arc and so it becomes crucial that we discuss Azure Arc first before we move on. Azure Arc
Before we start talking about Azure Stack HCI, let’s start with just HCI. HCI or “Hyperconverged Infrastructure” is a recent datacenter technology that lets you modernize and minimize your hardware footprint. A more “traditional” datacenter has different tiers of hardware (compute, storage and network) externally connected to each other, and as you can imagine this
Azure Update Management (AUM) is a free service that helps to deploy patches on servers running in Azure and On Premises (in your datacenter). It provides basic capabilities, but enough to control the whole patch process. While evaluating AUM on a Windows Server 2019 hosted on Azure I noticed that either monitoring with SCOM or
Most enterprises now have either moved to cloud, or are moving towards it. And why not? Running your workloads on cloud services such as Azure frees you up from a lot of maintenance and administrative overheads, and you can use this time to do something better. Here are some major benefits to moving to cloud:
Having worked with both SCOM and Azure Monitor, recently I was asked to compare them both and suggest the right choice. First off, I have a disclaimer to make – Azure Monitor is great, but it can not replace SCOM entirely, not just yet. SCOM 2019 was recently released and it came loaded with some
I was recently presenting a lecture speaking about how a large number of social networks cause companies to lose their control over communication channels with their customers. I was also explaining why it is a problem and how Azure serverless services can reduce the problem dramatically for less than 50$. The reaction from the audience
You must be logged in to post a comment.