Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Azure for Architects

You're reading from   Azure for Architects Implementing cloud design, DevOps, IoT, and serverless solutions on your public cloud

Arrow left icon
Product type Paperback
Published in Oct 2017
Publisher Packt
ISBN-13 9781788397391
Length 358 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (19) Chapters Close

Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
1. Getting Started FREE CHAPTER 2. Azure Design Patterns 3. Designing High Availability 4. Implementing Scalability 5. Cloud Security 6. Designing IoT Solutions 7. Designing and Implementing Data Solutions 8. Designing and Implementing Serverless Solutions 9. Designing Policies, Locks, and Tags 10. DevOps on Azure 11. Cost Management 12. Monitoring and Auditing

Scaling best practices


In this section, we will go through some of the best practices that applications should implement to take advantages of scalability capability provided by VMSS.

Prefer scaling out

Scaling out is a better scaling solution compared to scaling up. Scaling up or down means re-sizing of virtual machine instances. When a virtual machine is resized, it generally needs to be restarted, which has its own disadvantages. First, there is a downtime for the machine. Second, if there are active users connected to the application on that instance, they might face unavailability of application or they might even have lost transactions. Scaling out does not impact existing virtual machines. It provisions newer machines and adds them to the group.

Bare metal versus dormant instances

Scaling new instances can take two broad approaches. Either create the new instance from scratch, which means to install applications, configure, and test, while on the other hand, there can be dormant instances...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images