All about Service Oriented Architecture : SOAP / REST differences and usage

Service Oriented Architecture 
with 
REST/SOAP in SFDC

A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed.

The technology of Web Services is the most likely connection technology of service-oriented architectures. The following figure illustrates a basic service-oriented architecture. It shows a service consumer at the right sending a service request message to a service provider at the left. The service provider returns a response message to the service consumer.
 The request and subsequent response connections are defined in some way that is understandable to both the service consumer and service provider. How those connections are defined is explained in Web Services Explained. A service provider can also be a service consumer.
Service-oriented architecture
ref :http://www.service-architecture.com/articles/web-services/service-oriented_architecture_soa_definition.html



Difference between SOAP API and REST API ?




It is a pattern, a web service architecture, which specifies the basic rules to be considered while designing web service platforms. It typically uses HTTP as a layer 7 protocol, although this is not mandatory.

 The SOAP message itself consists of an envelope, inside of which are the SOAP headers and body, the actual information we want to send. It is based on the standard XML format, designed especially to transport and store structured data. SOAP may also refer to the format of the XML that the envelope uses.
SOAP is a mature standard and is heavily used in many systems, but it does not use many of the functionality build in HTTP. While some consider it slow, it provides a heavy set of functionality which is a necessity in many cases. It might now be the best solution for browser-based clients, due to its custom format.


It is another architectural pattern (resource-oriented), an alternative to SOAP. Unlike SOAP, RESTful applications use the HTTP build-in headers (with a variety of media-types) to carry meta information and use theGET, POST, PUT and DELETE verbs to perform CRUD operations. REST is resource-oriented and uses clean URLs (or RESTful URLs).

SOAP API
REST API
Simple Object Access Protocol
Representational State Transfer
It is based on standard XML format
It is based on URI
It works with WSDL
It works with GET, POST, PUT, DELETE
Works over with HTTP, HTTPS, SMTP, XMPP
Works over with HTTP and HTTPS

Exporting Data From Salesforce  REST or SOAP?


When to Use REST API

REST API provides a powerful, convenient, and simple REST-based Web services interface for interacting with Salesforce. Its advantages include ease of integration and development, and it’s an excellent choice of technology for use with mobile applications and Web projects. However, if you have a large number of records to process, you may wish to useBulk API.

When to Use SOAP API

SOAP API provides a powerful, convenient, and simple SOAP-based Web services interface for interacting with Salesforce.You can use SOAP API to create, retrieve, update, or delete records. You can also use SOAP API to perform searches and much more. Use SOAP API in any language that supports Web services.

For example, you can use SOAP API to integrate Salesforce with your organization’s ERP and finance systems, deliver real-time sales and support information to company portals, and populate critical business systems with customer information.

When to Use Bulk API

Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to query, insert, update, upsert, or delete a large number of records asynchronously by submitting batches which are processed in the background by Salesforce. SOAP API, in contrast, is optimized for real-time client applications that update small numbers of records at a time. Although SOAP API can also be used for processing large numbers of records, when the data sets contain hundreds of thousands of records, it becomes less practical. Bulk API is designed to make it simple to process data from a few thousand to millions of records.


API NameProtocolData FormatCommunication
REST APIRESTJSON, XMLSynchronous
SOAP APISOAP (WSDL)XMLSynchronous
Chatter REST APIRESTJSON, XMLSynchronous (photos are processed asynchronously)
Bulk APIRESTCSV, JSON, XMLAsynchronous
Metadata APISOAP (WSDL)XMLAsynchronous
Streaming APIBayeuxJSONAsynchronous (stream of data)
Apex REST APIRESTJSON, XML, CustomSynchronous
Apex SOAP APISOAP (WSDL)XMLSynchronous
Tooling APIREST or SOAP (WSDL)JSON, XML, CustomSynchronous


Bulk API

Bulk API is based on REST principles and is optimized for loading or deleting large sets of data. You can use it to query, insert, update, upsert, or delete many records asynchronously by submitting batches. Salesforce processes batches in the background.

Metadata API

Use Metadata API to retrieve, deploy, create, update, or delete customizations for your org. The most common use is to migrate changes from a sandbox or testing org to your production environment. Metadata API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.





Comments

Post a Comment

Popular posts from this blog

Apex Trigger Framework in Salesforce with best practise

Image
                                                            Trigger framework is not just needed for having single object per trigger guidance but also helps in different other reasons. According to the trigger framework : 1) Create a single trigger for each object. 2) A handler class which will call Action or Apex Interface based Trigger Framework Implementation One Trigger -One Object Policy Framework Implementation Bulkified Code  Avoid SOQL Queries or DML statements inside FOR Loops  Using Collections, Streamlining Queries, and Efficient For Loops   No  Hardcoding IDs Types of Framework available : 1.Handler/Controller Framework 2.Lightweight Apex Trigger Framework (Source:  http://chrisaldridge.com/triggers/lightweight-apex-trigger-framework/ ) Handler Framewo...
Read more

Apex Classes as REST Web Services in Salesforce

Introduction to Apex REST Salesforce platform is amazing and its lets your create your own lightweight  REST API using Apex. You can use this REST API to access force.com data, by authenticating the caller/consumer of API using standard oAuth and return data format support JSON/XML, purely depends how you want return back the data A few useful bits of information related to these REST APIs: Use standard HTTP verbs: GET, POST, PUT, PATCH, DELETE, and HEAD. You can use either HTTP or HTTPS. Use standard security to authenticate your REST calls via OAuth 2.0. Serialize your data in either XML or JSON format. This is done by defining your Apex class with the  @RestResource  annotation to expose it as a REST resource. Similarly, add annotations to your methods to expose them through REST. For example, you can add the @HttpGet  annotation to your method to expose it as a REST resource that can be called by an HTTP  GET  request.  Ap...
Read more

Apex CPU Limit Error : after running into an Apex CPU limit error whether anything is committed to the database

In a batch that updates an object that then activates a trigger,  would it stop at the object level or at the trigger level or does it depend on  when the apex limit is hit? Any governor limit, including Apex CPU timeouts, reverts all changes to the database for the  entire  transaction. That means no records are created, updated, deleted, undeleted, merged, converted, etc. The  only  exception to this rule is that any logs that are enabled will be preserved (in Setup > Monitoring > Debug Logs).  In the case of a batch, if it occurs in the start method, the entire batch is aborted, while ' if it occurs during an execute function, only that single batch is aborted (but prior batches are already committed, and future batches may still successfully commit), and  in the finish method, a governor limit would prevent chaining calls, sending emails, etc.
Read more