AZ900-AzureFundamentals-part-10.pdf
- 1. Retrieving data from memory is much faster than retrieving data from disk In-memory databases like Redis deliver microsecond latency by storing persistent data in memory Recommended Azure Managed Service Azure Cache for Redis Use cases : Caching, session management, gaming leader boards, geospatial applications In-memory Databases In-memory Databases 88
- 2. Databases - Summary Databases - Summary Database Type Azure Services Description Relational OLTP databases Azure SQL Database, Azure Database for MySQL, Azure Database for PostgreSQL etc. Transactional usecases needing predefined schema and very strong transactional capabilities (Row storage) Relational OLAP databases Azure Synapse Analytics Columnar storage with predefined schema. Datawarehousing & BigData workloads NoSQL Databases Azure Cosmos DB Apps needing quickly evolving structure (schema-less) MongoDB (document), Cassandra (key/value) and Gremlin (graph) In memory databases/caches Azure Cache for Redis Applications needing microsecond responses 89
- 3. Databases - Scenarios Databases - Scenarios Scenario Solution A start up with quickly evolving schema (table structure) Cosmos DB Single-digit millisecond response times for global application with millions of users Cosmos DB Transactional local database processing thousands of transactions per second Azure SQL Database OR Azure Database for MySQL OR Azure Database for PostgreSQL etc. Cache data (from database) for a web application Azure Cache for Redis Database for analytics processing of petabytes of data Azure Synapse Analytics 90
- 5. In a corporate network or an on-premises data center: Can anyone on the internet see the data exchange between the application and the database? No Can anyone from internet directly connect to your database? Typically NO. You need to connect to your corporate network and then access your applications or databases. Corporate network provides a secure internal network protecting your resources, data and communication from external users How do you do create your own private network in the cloud? Enter Azure Virtual Network Need for Virtual Network Need for Virtual Network 92
- 6. Your own isolated network in Azure Network traffic within a Virtual Network is isolated (not visible) from all other Azure Virtual Networks Each Virtual Network is created in a Region You control all the traffic coming in and going outside a Virtual Network (Best Practice) Create all your Azure resources (compute, storage, databases etc) within a Virtual Network Secure resources from unauthorized access AND Enable secure communication between your cloud resources Azure Virtual Network Azure Virtual Network 93
- 7. Different resources are created on cloud Databases, Compute (VMs) etc Each type of resource has its own access needs Load Balancers are accessible from internet (public resources) Databases or VM instances should NOT be accessible from internet ONLY applications within your virtual network should be able to access them(private resources) How do you separate public resources from private resources inside a Virtual Network? (Solution) Create different subnets for public and private resources Resources in a public subnet CAN be accessed from internet Resources in a private subnet CANNOT be accessed from internet BUT resources in public subnet can talk to resources in private subnet Need for Subnets Need for Subnets
- 8. 94
- 9. Every VM in a VNet is assigned a private IP address You can assign a public IP address and make it static as well! VMs in the same VNet can communicate using private IP addresses Even if they are in different subnets Network peering can be use to connect resources in different Virtual Networks Peered Virtual Networks can be in different regions Things to Remember - Virtual Network Things to Remember - Virtual Network 95
- 10. Azure network security Azure network security 96