If you're invested in Microsoft technologies, migrating to the cloud, using the Internet of Things (IoT) or considering a move to DevOps, you need to be aware of Azure. You’ve probably heard of Azure — especially if you're familiar with the concept infrastructure as code — but you may not be clear on its finer points. So, what is Azure? Simply put, Azure is Microsoft's public cloud service. Like its competitors, Amazon Web Services (AWS) and Google Cloud, Azure offers infrastructure-as-a-service (IaaS) but also storage, databases, active directory and a host of other services.
It's the new year; you’ve taken stock of your business priorities and you’ve made an important decision: your organization is moving to the cloud in 2019. That’s a good call — according to InfoWorld, 9 out of 10 companies will be running at least partially on the cloud by the end of this year. Now you just have to figure out how you’ll make that move. Will you migrate using a Lift and Shift approach? Will your strategy be Native Cloud?
It's a truism often tossed around among software engineers: the faster you can find a bug, the cheaper it is to fix it. Lately, we've been publishing a series about DevOps — the combination of development and operations teams, de-siloing IT, embracing automation and extending agile development practices past development and across the applications lifecycle. Speed is a huge benefit of DevOps — when workflows are automated, code is released faster.
A couple of weeks ago, I wrote a post about DevOps and why all industries need to implement it. But implementing DevOps is not as simple as combining your Development and Operations teams. Any organization that wants the full benefits of DevOps also has to automate things as much as possible: testing, compiling, deployment, even creation of your servers.
There is an unplanned outage and your company's most important application has gone down. It's taking forever to come online again. When you ask your IT department what's going on and when your application is going to be up and running, all you seem to hear is blame. The development team is mad at the operations team. The operations people are mad at the development people. Everything seems to be someone else's fault.