Azure SQL Database Serverless is a compute tier that is fundamentally different to the classic provisioned tiers that we are used to within Azure SQL Database. This is best used for those databases that are ever-changing with unpredictable patterns.
A look at the green benefits of cloud computing and how to achieve sustainable transformation.
Serverless computing is on an upward trend, so if you're considering it for your business, here's the benefits you should know.
Recent enhancements of Azure Files provide improvements to multiple data protection strategies. Azure Files provides a systematic approach to ensuring your data is available, backed up, and recoverable, here are some recent announcements in this area:
Ballard Chalmers is a Microsoft Gold Partner and Cloud Services Provider. Our focus, however, is less on the mainstream Cloud services such as Office 365, VoIP, Unified Comms and other SaaS cloud software platform such as Salesforce. Our focus is on custom cloud application development and systems integration.
One of the benefits of using Azure for Serverless work is not having to think about scaling for the most part. There is something built from Service Bus...
Azure Active Directory B2C (Business to Customer) is an identity management service that enables you to customise and control how customers sign up, sign in, and manage their profiles when using an application. Azure Active Directory B2C enables these actions while protecting the identities of your customers at the same time.
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.
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.