Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Implementing Azure Cloud Design Patterns
  • Table Of Contents Toc
  • Feedback & Rating feedback
Implementing Azure Cloud Design Patterns

Implementing Azure Cloud Design Patterns

By : Michalski, Stefano Demiliani
2.8 (5)
close
close
Implementing Azure Cloud Design Patterns

Implementing Azure Cloud Design Patterns

2.8 (5)
By: Michalski, Stefano Demiliani

Overview of this book

A well designed cloud infrastructure covers factors such as consistency, maintenance, simplified administration and development, and reusability. Hence it is important to choose the right architectural pattern as it has a huge impact on the quality of cloud-hosted services. This book covers all Azure design patterns and functionalities to help you build your cloud infrastructure so it fits your system requirements. This book initially covers design patterns that are focused on factors such as availability and data management/monitoring. Then the focus shifts to complex design patterns such as multitasking, improving scalability, valet keys, and so on, with practical use cases. The book also supplies best practices to improve the security and performance of your cloud. By the end of this book, you will thoroughly be familiar with the different design and architectural patterns available with Windows Azure and capable of choosing the best pattern for your system.
Table of Contents (11 chapters)
close
close

SLA

Although the term, SLA has already been mentioned, the first question is what is an SLA? Although there are several answers (any infrastructure architect among you can confirm that), I would like to confine myself to the following simple answer:

An SLA is a contract between you and your cloud service provider that guarantees you a certain degree of availability for services booked. That sounds very good, but in real life that just means that you get your money back if the guarantee is not respected.

Nevertheless, we should now pursue the question: how do I determine a degree of availability? For the degree of availability, we first need the desired uptime. This can vary according to your needs. For example, if you operate a webshop, the targeted uptime is 24 hours x 7 days or 168 hours per week or 8,760 hours per year. But if you only have one application for...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Implementing Azure Cloud Design Patterns
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist download Download options font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon