Azure Content Delivery Network (CDN) is a CDN service provided by Azure Cloud Platform that enables storing and accessing data on different content servers and locations – used by online or cloud services. A CDN store the content cached on the edge servers that are available in the POP locations to reduce latency. Azure CDN is important for us which requires multiple hits to boost up the process of our applications.
Benefits of using Azure CDN –
Better performance and improved user experience for end users
Large scaling to better handle instant high loads
Distribution of user requests and serving of content directly from edge servers so that less traffic gets sent to the origin server.
The Internet of Things (IoT) is a network of physical devices that link to and share data with other devices and services via the Internet or another communication network. There are presently over ten billion connected devices worldwide, with more being added every year. Anything that has the required sensors and software can be connected to the internet. The following tools have enabled IoT:
Access to low cost, low power sensors.
Various protocols enable internet connectivity.
Cloud computing platforms such as Azure.
What is Azure IoT Central?
Azure IoT Central is a platform as a service (PaaS) for creating, managing, and maintaining enterprise-grade IoT solutions. Choosing to build with IoT Central allows you to focus your time, money, and energy on transforming your company with IoT data, rather than just managing and updating a complex and ever-changing IoT infrastructure.
In organizations, employees often need access to various Azure services to perform their tasks. They can use services like SQL database or Azure container services when the system administrator assigns them a user id and password for each service. However, managing multiple user logins for each service can be a hassle for administrators, especially in organizations with over 1000 employees. Azure Active Directory (AD) helps solve this issue by enabling administrators to manage multiple user logins in a centralized manner.
While working on Azure, you might come across a requirement that says the resources being deployed should be in accordance with the organization’s policies. Suppose you might want to grant a particular or a set of permissions on the resource group or on the management group so that the owner of it should be restricted like denying deploying of resources by enforcing resource tagging, region enforcement, allowing approved Virtual machines (VM) images, and many more.
In this blog, we will try to resolve these issues by applying Azure policies.
First, let’s get familiar with the azure policy.
The azure policy is a service that has been designed to help you enforce different rules and to act based on the rule’s effect on your Azure resources. You can use it to create, assign and manage policies. Azure policy evaluates your resources for non-compliance with assigned policies and performs the assigned effect.
There are different application categories in the general application world, but we usually define them in two major types, i.e., stateless and stateful applications.
To have a clearer perspective, we can say that API-based applications are generally stateless, and databases are stateful. In simple words or definition, a stateless application is an application that doesn’t save or persists the client data. On the other hand, a stateful application saves data about each client and uses it for other requests.
In the older days, when we didn’t have a concept of containers and container orchestrators, there was a common way to manage both types of applications: server. For example- API and database-based applications get hosted on servers but with different configurations depending on the resource requirements.