This is a
continuation of an article that describes operational considerations for hosting
solutions on Azure public cloud.
1.
When an application is migrated to Azure, its
storage can remain the same format as before. For example, if file storage was
used, NFSv3 can continue to be used by using Azure Storage V2.
2.
General-purpose v2 accounts deliver the lowest
per-gigabyte capacity prices for Azure Storage, as well as industry-competitive
transaction prices. General-purpose v2 accounts support default account access
tiers of hot or cool and blob level tiering between hot, cool, or archive.
3.
Archive storage tier does not provide immediate
data access. That can take hours to rehydrate. If we need immediate access,
change the access tier to hot or cool. A v1 storage account can be upgraded to
either hot or cool storage tier.
4.
Costs for storage tier is based on amount of
data stored depending on the access tier, the data access cost, the transaction
cost, the geo-replication data transfer cost, the outbound data transfer cost,
and the changing storage access tier. The primary access pattern for the blob
storage in terms of reads and writes and their comparisons determines the cost
savings. All storage accesses can be monitored, and metrics emitted include
capacity costs, transaction costs, and data transfer costs.
5.
Elastic pools can help manage and scale multiple
databases in Azure SQL Database.
Traditionally, there were two options: over-provision resources based on
peak usage and overpay, or Under-provision to save cost, at the expense of
performance and customer satisfaction during peaks. Elastic pools solve this
problem by ensuring that databases get the performance resources they need when
they need it. They provide a simple resource allocation mechanism within a
predictable budget
6.
ExpressRoute, VPN Gateway and Virtual network
peering provide different levels of functionality. If we want private
site-to-site connectivity, we can use ExpressRoute. If we want secure
site-to-site VPN connectivity, we can use virtual network site-to-site
connection. If we want secure point to
site connectivity, we can use virtual network point-to-site connection. We must have a private site-to-site
connectivity, a secure site to site VPN connectivity, and a secure point to site connectivity only
in that order.
7.
No comments:
Post a Comment