Book Image

A Developer's Guide to Cloud Apps Using Microsoft Azure

By : Hamida Rebai Trabelsi
Book Image

A Developer's Guide to Cloud Apps Using Microsoft Azure

By: Hamida Rebai Trabelsi

Overview of this book

Companies face several challenges during cloud adoption, with developers and architects needing to migrate legacy applications and build cloud-oriented applications using Azure-based technologies in different environments. A Developer’s Guide to Cloud Apps Using Microsoft Azure helps you learn how to migrate old apps to Azure using the Cloud Adoption Framework and presents use cases, as well as build market-ready secure and reliable applications. The book begins by introducing you to the benefits of moving legacy apps to the cloud and modernizing existing ones using a set of new technologies and approaches. You’ll then learn how to use technologies and patterns to build cloud-oriented applications. This app development book takes you on a journey through three major services in Azure, namely Azure Container Registry, Azure Container Instances, and Azure Kubernetes Service, which will help you build and deploy an application based on microservices. Finally, you’ll be able to implement continuous integration and deployment in Azure to fully automate the software delivery process, including the build and release processes. By the end of this book, you’ll be able to perform application migration assessment and planning, select the right Azure services, and create and implement a new cloud-oriented application using Azure containers and orchestrators.
Table of Contents (20 chapters)
1
Part 1 – Migrating Applications to Azure
6
Part 2 – Building Cloud-Oriented Applications Using Patterns and Technologies in Azure
10
Part 3 – PaaS versus CaaS to Deploy Containers in Azure
14
Part 4 – Ensuring Continuous Integration and Continuous Deployment on Azure
17
Assessments

Solution architecture

Whether you’re planning to migrate an existing application to microservices or adopt a microservice architecture from scratch, there are some important architectural decisions that you need to make upfront. In this section, we’ll discuss some of the key architectural principles for how we define a microservice and its components.

The use case presented previously has a monolithic solution that uses one SQL Server database, with multiple backups every day. The services share the same data model because every web API service targets the same data:

Figure 4.3 – Monolithic solution architecture

Figure 4.3 – Monolithic solution architecture

Our healthcare solution uses a traditional three-tier application architecture; the client applications include mobile applications and web applications. The presentation layer includes .NET Framework 4.5, and we also have Xamarin.Forms, Web App Model-View-Controller (MVC), and AngularJS, as well as mobile applications built...