Automated Builds, Continuous Integrations, DevOps, Oh my!! There are a ton of buzz words surrounding the different methods and ideas for managing hosting environments and deployments. One of the greatly implied concepts that isn’t really discussed very much is the importance of keeping different hosting environments for the same application (ala Dev, Test, UAT, Staging, Production, etc.) separate / isolated. During the development and maintenance processes these different environments can easily be mixed and messed with. This article will explain some details on why they should be kept separated, and how to keep them separated. Read More
The new Azure Disk Encryption feature was introduced into Public Preview last November. It allows for Virtual Machines (VMs) hosted within Azure to be encrypted using keys and policies controlled by Azure Key Vault. Read More
The Microsoft Azure IoT (Internet of Things) Hub is a set of features designed to help control, monitor and connect millions of IoT devices in a reliable and secure manner. While IoT solutions can be built using Azure, the IoT Hub provide functionality to help make the entire system both easier to implement as well as more secure. Read More
What really is a Microservices Architecture? The term “Microservices” has become fairly popular in recent years, and has coincided largely with the increasingly popular move to hosting applications in the cloud. With a better understanding of what a Microservices Architecture is and how to implement one, you’ll see that it’s not just a Cloud Architecture pattern. Read More
Azure has come along way in regards to features and pretty much every aspect of the service since it’s initial launch in 2010. In the last 5 years, Microsoft has spent a huge amount of money growing out this new cloud business. Now that Azure has been tested and proven over time, it’s gained the credibility necessary to enable Microsoft to migrate its enterprise service business to the cloud.
Azure is a huge piece to the future success of Microsoft.
One of Microsoft’s biggest strengths is in building development and hosting platforms. As more businesses are looking to cloud based services to cut hosting costs and gain efficiencies; Microsoft has been building out the Azure platform and positioning itself as a leader in the very cloud these businesses are looking for. Read More
The question of “Where do I start?” can be confusing if you’ve never studied for or taken a Microsoft Certification exam before. It can also be a bit daunting if you don’t know anyone who has done it themselves either. Do not let this discourage you. It may be a bit confusing, but it’s actually rather simple. This post will outlines the main steps necessary as well as the main resources you’ll need to begin, study, eventually pass an exam, and finally obtain a Microsoft Azure Certification yourself!
Update 9/30/2016: This week Microsoft announced some really big and amazing changes to the Microsoft Certification program and how the Azure certification exams fit in with MCSD and MCSE certifications. As a result, you want to reference the 2016 Edition of Where to start with Azure Certification article instead.
Just as all Azure Web Apps need configuration values, most applications also need to have database Connection String values configured. With Azure Web Apps the Connection Strings are stored/retrieved in a very similar fashion as Azure Web App Application Settings. Connection Strings are also Key / Value pairs of String values, but are separated out into their own section.
Connection Strings are typically used to store the connection information for one or more databases the Web App needs to connect to for storing and retrieving data. The Connection String types supported are SQL Database, SQL Server, MySQL and Custom. Most often the Connection Strings used will be for some kind of SQL RDMS, but the Custom type allows for an additional Connection String to be configured any other type of database connection necessary.
As with Application Settings, the Connection Strings are accessed as normal from .NET code and the values will come from what is set within the Azure Management Portal. In other development environments (Node.js, Java, PHP, Python) the Connection Strings are exposed to code as Environment Variables. Additionally, the Connection Strings are editable within the Azure Management Portal, but are read-only when access through code. Read More
All web applications have some kind of configurations necessary. The method of storing and accessing these settings varies on different web application platforms. In ASP.NET they are normally stored within <appSettings> element of the web.config file. The Microsoft Azure Web Apps Service allows for these application settings to be configured within the Azure Web App configurations in the cloud, and then subsequently accessed from application code as needed. With .NET applications the application settings are accessed exactly as AppSettings contained within the web.config file. In other web platforms (Java, Node.js, PHP and Python) the application settings are access via Environment Variables.
Application Settings are stored as a Key / Value pair. These are both stored as String values. Read More