The purpose of this article is to discuss what Azure SQL Database Managed Instance is. This will then lay a foundation to explore the capabilities of this deployment model. We will discuss some advantages it can bring to your infrastructure with a cross comparison against on-premises SQL Server. Finally, we look at some important networking configuration that you will need to be aware of when evaluating it.
The decision to modernise your data estate usually begins with recognising that your existing systems are no longer sufficient to support your enterprise’s requirements. Here in this infographic, Microsoft provide 3 reasons to get started with modernising your data estate now.
There is an abundance of Azure development information to be found on Twitter and to get the most from the platform it helps to know where to go. To narrow it down, we are highlighting here what we consider some key accounts to follow.
After starting with the database, we moved on to how to expose this data and add our business logic. Our traditional approach would have been to use a Web API but Azure Functions offered a way to completely remove any infrastructure management and scale instantly. It also offered the potential to use micro billing and only pay for calls being made although at a performance cost – more on that later.
Using a DTU (Database Transaction Unit) based model was always the way to size and configure an Azure SQL Database, that was until recently where Microsoft developed a vCore based model to size cloud-based databases. This article will compare at a high level these very different options and why you would select one model over the other.
The first decision we made with the new application was to go with a Document Database and for performance and scalability reasons, Azure Cosmos DB was the natural choice. The application would have few related objects and so lent itself to the Document DB model although it would not be likely to the scale to the size where it was a no-brainer.
The world of n-tier architectures is dead. Well maybe not quite dead, but it is certainly not the foundation of design for new systems that it has been for many years. The advent of cloud systems along with the improvements in development tooling has pushed architects to design scalable systems that make the most of the cloud platforms and allow the focus to shift to business logic, rather than the platforms needed to deliver applications.
If you are running SQL Server 2008 or 2008 R2, these versions are reaching the end of their support lifecycle on 9 July 2019.
SQL Server 2008 and 2008 R2 End of Support means the end of security updates from Microsoft. To overcome this, Microsoft recommends upgrading to the current version of SQL Server on-premises, and/or migrating to Azure; both of these options provide you with the most advanced security, performance, and innovation.
I have been recently exploring creating sites with Flow off the back of a list. I’d done this previously with Azure Functions very successfully but wanted to see if Site Scripts and Site Designs could remove that extra step. In short: Yes you can!