Book Image

Implementing Azure Solutions - Second Edition

By : Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke
Book Image

Implementing Azure Solutions - Second Edition

By: Florian Klaffenbach, Markus Klein, Sebastian Hoppe, Oliver Michalski, Jan-Henrik Damaschke

Overview of this book

<p>Microsoft Azure offers numerous solutions that can shape the future of any business. However, the major challenge that architects and administrators face lies in implementing these solutions. </p><p>Implementing Azure Solutions helps you overcome this challenge by enabling you to implement Azure Solutions effectively. The book begins by guiding you in choosing the backend structure for your solutions. You will then work with the Azure toolkit and learn how to use Azure Managed Apps to share your solutions with the Azure service catalog. The book then focuses on various implementation techniques and best practices such as implementing Azure Cloud Services by configuring, deploying, and managing cloud services. As you progress through the chapters, you’ll learn how to work with Azure-managed Kubernetes and Azure Container Services. </p><p>By the end of the book, you will be able to build robust cloud solutions on Azure.</p>
Table of Contents (14 chapters)

Hybrid cloud patterns

Now that we have an overview of what Azure Stack is, how it works, and how we could work with it, let's go on and discuss some scenarios where Azure Stack could fit. Here are some examples:

Basically, you should in general think about public Azure and how to move your IT services to it. If there is a reason why a service does not fit public Azure, Azure Stack might work.

The general scenarios for Azure Stack are as follows:

  • Edge and disconnected solutions: Edge and disconnected solutions are everything when not much internet connectivity is available or not intended. Therefore, the disconnected mode is suitable, because with Azure AD an internet connection is really needed.
  • Data sovereignty: Data sovereignty is the most important reason, as if a customer is not able to, not willing to, or does not have to move specific data to the public cloud, Azure Stack fits completely, as stack lives on the premise, where the data needs to reside.
  • ...