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
SOA Patterns with BizTalk 2013, Second Edition

You're reading from   SOA Patterns with BizTalk 2013, Second Edition Learn how to create and implement SOA strategies on the Microsoft technology stack using BizTalk Server 2013 and Azure Integration platforms

Arrow left icon
Product type Paperback
Published in Jun 2015
Publisher
ISBN-13 9781784396466
Length 508 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (16) Chapters Close

Preface 1. Building BizTalk Server 2013 Applications 2. Windows Communication Foundation Primer FREE CHAPTER 3. Using WCF Services in BizTalk Server 2013 4. REST and JSON Support in BizTalk Server 2013 5. Azure BizTalk Services 6. Azure Service Bus 7. Planning Service-oriented BizTalk Solutions 8. Schema and Endpoint Patterns 9. Asynchronous Communication Patterns 10. Orchestration Patterns 11. Versioning Patterns 12. Frameworks and Tools 13. New SOA Capabilities in BizTalk Server 2013 – Azure Hybrid Patterns 14. What's New and What's Next? Index

Why REST services

A REST-based service is best suited for limited bandwidth and resources where you need to process simple Create, Read, Update, Delete (CRUD) type operations using the following verbs:

  • GET
  • POST
  • PUT
  • DELETE

Also, REST is a platform and language independent service, which makes it ideal as an integration protocol.

It uses a lightweight protocol such as HTTP to send messages in a simple XML format, or other formats such as JSON or plain text. TCP may also be used, but HTTP is more commonly used.

REST services are totally stateless in operation. This allows greater scalability since the server does not have to maintain the session state. What this essentially means is that the client must include all the information required for the server to fulfill each request.

For a comparison between messaging based on SOAP and REST, please refer to the blog post at http://connectedcircuits.wordpress.com/2013/02/16/what-to-use-soap-or-rest/.

A RESTful API should adhere to the following specifications...

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