Chapter 8
Advanced Configuration
IN THIS CHAPTER:
- Scale your mobile service so that it can support a large number of users
- Utilize an existing database as the backing data store for your mobile service
- Integrate WAMS into your operations infrastructure
WROX.COM CODE DOWNLOADS FOR THIS CHAPTER
The wrox.com code downloads for this chapter are found at http://www.wrox.com/go/windowsazuremobileservices on the Download Code tab. The code is in the Chapter 8 download and individually named according to the names throughout the chapter.
Floating just under the surface of all that you have learned about Windows Azure Mobile Services (WAMS) to this point is a concept that might surprise you. At its heart, WAMS is just a combination of Windows Azure Web Sites and SQL Azure. Think of it like this: The endpoints that you communicate with using REST are services that could be constructed using WCF. Well, maybe not easily, but certainly feasibly. The data that is received, stored, and retrieved is persisted in a SQL Azure database. Could you create something that does what WAMS does? Of course you could. The challenge of building Windows Azure Mobile Services is not a technological one, nor are the benefits found in the technology.
What WAMS brings to the table is a combination of prebuilt functionality ready for you to take advantage of, along with the ability to extend its capabilities in a number of different directions. In Chapter 7, you looked at how to extend the functionality of WAMS ...
Get Windows Azure Mobile Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
