Wednesday, March 21, 2018
Friday, March 16, 2018
After becoming an increasing threat to Amazon in the public cloud space, and in the fourth quarter increased its market share from 16 to 20 percent, according to KeyBanc analysts, Microsoft Finally announced its plans for a major expansion of the Microsoft Cloud with the launch of its first cloud regions in the Middle East. These new regions, which are scheduled to go online in 2019, will be located in Abu Dhabi and Dubai and will host the company’s usual Azure, Office 365 and Dynamics 365 services.
“Microsoft has been present in the Middle East for more than two decades and is deeply invested in the region in many ways,” said Sayed Hashish, regional general manager, Microsoft Gulf, in today’s announcement.
"We see enormous opportunity in MEA (Middle East and Africa) for cloud technology to be the key driver of economic development, as well as provide sustainable solutions to many pressing issues such as youth employability, education and healthcare," Samer Abu-Ltaif, president of Microsoft Middle East Africa, said in a press release.
It’s worth noting that Amazon, too, has already announced its plans for a region in Bahrain, which will open in about a year, while Google has not announced any plans to enter this market yet.
In addition to the new Middle East regions, Microsoft also today announced its first region in Switzerland (with data centers around Geneva and Zürich), which is scheduled to go online in 2019. In Germany, the company is launching an additional cloud region and in France, the Microsoft Cloud is now generally available.
In total, Microsoft now offers 50 regions around the globe, with plans for 12 new regions in the works.
You could have more details in https://www.cnbc.com/2018/03/14/microsoft-plans-to-open-its-first-middle-east-data-centers-in-2019.html
Wednesday, March 07, 2018
These are the sub-topics that you have to cover in the Azure Compute Infrastructure
topic of Exam 70-535 (Architecting Microsoft Azure Solutions). This sub-topic should cover 10- 15% of the exam. For the complete list of the seven topics, please refer to the first post of this series :
• Design solutions using virtual machines
• Design VM deployments by leveraging availability sets, fault domains, and update domains in Azure; use web app for containers; design VM Scale Sets; design for compute-intensive tasks using Azure Batch; define a migration strategy from cloud services; recommend use of Azure Backup and Azure Site Recovery
• Design solutions for serverless computing
• Use Azure Functions to implement event-driven actions; design for serverless computing using Azure Container Instances; design application solutions by using Azure Logic Apps, Azure Functions, or both; determine when to use API management service
• Design microservices-based solutions
• Determine when a container-based solution is appropriate; determine when container-orchestration is appropriate; determine when Azure Service Fabric (ASF) is appropriate; determine when Azure Functions is appropriate; determine when to use API management service; determine when Web API is appropriate; determine which platform is appropriate for container orchestration; consider migrating existing assets versus cloud native deployment; design lifecycle management strategies
• Design web applications
• Design Azure App Service Web Apps; design custom web API; secure Web API; design Web Apps for scalability and performance; design for high availability using Azure Web Apps in multiple regions; determine which App service plan to use; design Web Apps for business continuity; determine when to use Azure App Service Environment (ASE); design for API apps; determine when to use API management service; determine when to use Web Apps on Linux; determine when to use a CDN; determine when to use a cache, including Azure Redis cache
• Create compute-intensive application
• Design high-performance computing (HPC) and other compute-intensive applications using Azure Services; determine when to use Azure Batch; design stateless components to accommodate scale; design lifecycle strategy for Azure Batch