Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Microsoft System Center Orchestrator 2012 R2 Essentials

You're reading from   Microsoft System Center Orchestrator 2012 R2 Essentials

Arrow left icon
Product type Paperback
Published in Aug 2015
Publisher
ISBN-13 9781785287589
Length 182 pages
Edition 1st Edition
Arrow right icon
Toc

Scalability

This question was set here on purpose due to the fact that many people still get confused about scalability and High Availability, even though both topics are quite different from one another. You'll be using High Availability to keep your service available as much as possible during time, thus improving the user experience and also the availability of your service. You'll however, implement scalability to ensure that the service is responding to the service requests (or demand) and therefore, being provided efficiently and in a timely fashion. Don't forget that scalability is used not only to add resources to a service, but also to reduce the service resources, depending on the need and the scope of that same service.

You'll usually start the Orchestrator architecture with a single server deployment to see how it goes and how you can answer the automation requests you'll find. It will be during the technology lifetime that you'll see the demand...

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 $19.99/month. Cancel anytime
Banner background image