Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Building Web Services with Windows Azure (new)
  • Table Of Contents Toc
Building Web Services with Windows Azure (new)

Building Web Services with Windows Azure (new)

By : Kaufman, Nikhil Sachdeva
4 (3)
Buy this Book
close
close
Building Web Services with Windows Azure (new)

Building Web Services with Windows Azure (new)

4 (3)
By: Kaufman, Nikhil Sachdeva
Buy this Book

Overview of this book

If you are a .NET developer who wants to develop end-to-end RESTful applications in the cloud, then this book is for you. A working knowledge of C# will help you get the most out of this book.
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
Introduction
Icon
Introduction
Icon
Getting to know HTTP
Icon
HTTP 2.0
Icon
The rise of REST
Icon
The REST style of services
Icon
Web API and Microsoft Azure
Icon
Summary
2
1. Getting Started with the ASP.NET Web API
Icon
1. Getting Started with the ASP.NET Web API
Icon
The ASP.NET Web API framework
Icon
Background
Icon
Building blocks
Icon
Design principles behind the ASP.NET Web API
Icon
Application scenarios
Icon
Behind the scenes with the ASP.NET Web API
Icon
Routing and dispatching
Icon
Creating our first ASP.NET Web API
Icon
Testing the Web API
Icon
Committing changes to Git
Icon
Deploying the ASP.NET Web API using Azure Websites
Icon
Continuous Deployment using Azure Websites
Icon
Summary
3
2. Extending the ASP.NET Web API
Icon
2. Extending the ASP.NET Web API
Icon
Attribute routing
Icon
Content negotiation
Icon
Securing the ASP.NET Web API
Icon
Hosting
Icon
Summary
4
3. API Management
Icon
3. API Management
Icon
Azure API Management
Icon
Managing a Web API
Icon
Consuming the Web API
Icon
Summary
5
4. Developing a Web API for Mobile Apps
Icon
4. Developing a Web API for Mobile Apps
Icon
Azure Mobile Services
Icon
Creating a Web API using Mobile Services
Icon
Leftovers
Icon
Summary
6
5. Connecting Applications with Microsoft Azure Service Bus
Icon
5. Connecting Applications with Microsoft Azure Service Bus
Icon
Azure Service Bus
Icon
Summary
7
6. Creating Hybrid Services
Icon
6. Creating Hybrid Services
Icon
Service Bus Relay Service
Icon
BizTalk Hybrid Connect
Icon
Summary
8
7. Data Services in the Cloud – an Overview of ADO.NET and Entity Framework
chevron up
Icon
7. Data Services in the Cloud – an Overview of ADO.NET and Entity Framework
Icon
Key layers of distributed applications
Icon
Data and data access technologies
Icon
Creating a data source for a Web API application
Icon
Summary
9
8. Data Services in the Cloud – Microsoft Azure Storage
Icon
8. Data Services in the Cloud – Microsoft Azure Storage
Icon
Microsoft Azure Storage
Icon
Using Microsoft Azure Storage in the Web API application
Icon
Summary
10
9. Data Services in the Cloud – NoSQL in Microsoft Azure
Icon
9. Data Services in the Cloud – NoSQL in Microsoft Azure
Icon
Understanding NoSQL
Icon
An overview of Microsoft Azure NoSQL technologies
Icon
DocumentDB in a Web API application
Icon
MongoLab MongoDB on Microsoft Azure
Icon
Summary
11
Index
Icon
Index

Chapter 7. Data Services in the Cloud – an Overview of ADO.NET and Entity Framework

Every application that is dependent on data should have storage that will be used for that data. It can be memory storage, a file on the local or remote disk, or a database. Each storage type has its own characteristics; for example, if we use memory or a local disk, we are merging two different application layers—the data access layer and the store itself—and we don't have a really effective way of managing the fault tolerance of our solution as it is limited to local storage. Sometimes this is good—for example, when we are developing an application that will be or should be small and fault-tolerant. If we want to develop an application that is fault-tolerant (for example, if one server does not respond, the user would still have access to his information) and have code that is easy to maintain, we have to split application layers.

In this chapter we will go through...

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.
Building Web Services with Windows Azure (new)
End of Section 8
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist 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
Order Page Read Now

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