What is Integration?
Integration is the most common way of bringing at least two frameworks together, which permits you to smooth out discrete cycles.
Consider cases in your innovation stack in which data is kept in one framework yet in addition expected in another. By coordinating them, you can without much of a stretch deal with all that data through different business processes that stumble into various frameworks.
For what reason is Integration significant?
We live in an advanced period and we continually need to work on our productivity and our clients’ insight to stay cutthroat interestingly, a framework works in separation now.
We want to turn out to be better and better at coordinating our frameworks so we can do it quickly and in an adaptable manner. Integration is the method involved with bringing at least two frameworks together, which permits you to smooth out discrete cycles.
Consider cases in your innovation stack in which data is kept in one framework yet additionally expected in another. By incorporating them, you can undoubtedly deal with all that data through various business processes that stumble into different frameworks.
For what reason is Mix significant?
We live in an advanced period and we continually need to work on our effectiveness and our client’s insight to stay serious interestingly, a framework works in disengagement now. We want to turn out to be better and better at incorporating our frameworks so we can do it quickly and in a versatile way.
What is an API?
API stands for Application Programming Interface. It is the means that allows two applications to talk to each other.
Or instance, when you utilize an application on your telephone, the application associates with the web, snatch information from a server, and presents it back to you in a clear configuration. With the right API, this entire cycle ought to occur easily.
There are various kinds of APIs that I will cover later in the ‘Salesforce Integration Capabilities’ part.
Types of Salesforce Integration Architectures
- Point-to-point integration
- Hub-and-spoke integration
- Enterprise Service Bus integration (ESB)
Point-to-Point Integration
One-to-one integration, a highlight point framework mix makes an impression on another framework by means of a 1-1 relationship. Assume you have a business application that sends new requests data to a charging framework, to a delivery application, and to a global positioning framework, all independently similar to possess little coordination.
In the event that you need the following and the transportation to convey, that is one more incorporation that should be set up.
This type of integration has many drawbacks. It is expensive to build and maintain, and if you ever want to replace one of these systems, you have to build multiple new integrations to get it to reconnect to the same systems.
Hub-and-Spoke Integration
With hub-and-spoke integration, you have an incorporated center point framework that works with correspondence between the frameworks. The center is answerable for directing all traffic, and you just need to assemble one association for each new framework, which is a big improvement on point-to-point integration.
Enterprise Service Bus Integration (ESB)
Enterprise Service Bus (ESB) marks the advancement of the center and-talked incorporation design model. The thing that matters is the mixing motor used to make associations between associated programming applications and frameworks.
Use ESB if you need to do any of the following with your ‘messages’:
- Routing: If you want a ‘message’ to go from one system (A) to another system (B) or several systems.
- Orchestration: The order in which the transactions occur. For example, you might need a series of events to happen in a specific order. Imagine a scenario where one system needs to update something and give a response before that response can be used on a separate system.
- Transformation: If you want a ‘message’ to go from one system (A) to another system (B), but System B doesn’t speak the same language as System A, the bus first transforms that message into System B’s language.
- Security: It can provide authentication and authorization to meet security requirements.
Salesforce Integration Capabilities
A high-functioning API that allows any two applications to communicate with each other. When we are talking about integrations, it is important that we understand their timing and direction. The timing falls into two categories:
- Synchronous: You make a call to another system, but you have to wait for a response in return. The processing won’t continue until the response has been received.
- Asynchronous: You make a call to another integrated system, but you don’t have to wait for a response – further processing can continue. For example, if you have a background job that will take a long time to process, you don’t want to wait for the response from that to be created (as you risk a timeout).
Integration capabilities are what Salesforce gives us in order to build these integrations. Here are eight that you should know about:
1. REST API
This focuses on data-based operations:
- GET to query a database
- POST to create a record
- PUT to update
- PATCH
- DELETE
REST API is best for web or portable applications. As to designs, it utilizes XML or JSON. JSON works better with information and is best for web or portable applications. This implies that REST doesn’t utilize a lot of data transfer capacity and is effortlessly consumed by internet browsers.
As far as timing, REST is simultaneous. For instance, you send a POST solicitation to make a record in Salesforce and you will get a reaction with regards to whether or not it was fruitful.
Salesforce Workbench is a set-up of apparatuses that permits you to collaborate with Salesforce utilizing APIs. I suggest you do some investigating with Workbench to get to know the REST API.
2. SOAP API
SOAP API was more commonly used by older systems, but you may still come across it. It’s best for system-to-system integrations, back-end system communication, and for applications that require formal hand-off (contracts) between the API and the consumer (thanks to WSDL).
While it’s reliable and well-established, it tends to be slower and use more bandwidth than REST. It uses XML for very structured payloads and is asynchronous, meaning that it doesn’t need to wait for a response and can continue with other processing without causing blocks.
3. Bulk API
The Bulk API in Salesforce can handle high volumes of messages – up to 100 million records per rolling 24-hour timeframe. These APIs increase stability, allow you to monitor your jobs, and control your message loads.
It’s best suited for initial data migration as this option will allow you to load your organization’s data into Salesforce quickly. It allows you to control process jobs in serial mode (one after the other) or in parallel (multiple batches at the same time), and it’s clever enough to do automatic file batching.
As I’m sure you already guessed, it is asynchronous. You upload your load and then come back later to check the results.
4. Streaming API
There are two correspondence models: ‘Solicitation and Response’ and ‘Occasion Driven’. The Streaming API depends on the distribute/buy-in model, is an exceptionally effective method for sending notices, and is the premise of Event-Driven Architecture.
There are four Streaming APIs:
- Generic
- PushTopic
- Platform Events
- Change Data Capture
They are completely assembled utilizing CometD innovation.
This implies there is an Enterprise Messaging Bus that permits an Event Producer to distribute a Message to a feed so any Event Consumer (bought into it) can get that transmission. Stage Events improve on the method involved with imparting changes in information and permit us to have a close to constant reconciliation among Salesforce and outer frameworks.
5. Outbound Message
Messages can be sent to any SOAP-based server endpoint that has a custom listener service. The message contains the fields you select when setting it up and is sent to your specified endpoint URL. This integration is asynchronous, but the integrated system will send back a message of acknowledgment. If Salesforce doesn’t receive the acknowledgment, it will continue retrying for 24 hours before notifying the System Admin user/s that the message was not successfully delivered.
Note that Outbound Messages are not designed to provide near real-time integration and Salesforce advises that the Streaming API should be used instead if that’s what you need.
6. Web Service Callouts
Callouts occur when Salesforce is calling out to another system (Salesforce is the ‘initiator’). For example, when a user updates an Account’s address field, Salesforce calls out to an address database to verify the new address (note: callouts are triggered by other events, not just field changes).
Web Service Callouts are:
- Free to use but are programmatic, you will need a developer to write the actions.
- Used when your timing requirements are synchronous, or you expect a quick response for asynchronous (note: callouts invoked using an Apex trigger must be tagged as asynchronous).
- Good if your data load is small (Request and Response < 3 MB).
7. Salesforce Connect
With Salesforce Connect, you can see and edit data from an external system in Salesforce. This is known as ‘Data virtualization’ – data is shown in Salesforce when required, but does not persist in Salesforce (we’ll revisit Data virtualization later). This is a declarative but paid feature. It does allow you to save up on data storage space because data is accessed in real time, and not stored in or copied into Salesforce.
How Salesforce Connect works:
You make another External Object (finishing __x) that uncovered the outside information.
It permits Lookups to different items (for example you could have an Opportunity in Salesforce that showcases Invoice and Invoice Line Items from an outside charging framework).
Information is introduced when called and you can run reports, make related records, or run SOQL and SOSL.
It tends to be utilized to associate with Salesforce organizations.
8. Heroku Connect
Heroku is a cloud platform available as a platform-as-a-service (PaaS) that allows your business to develop, deliver, monitor, and scale various apps to bypass infrastructure obstacles. Heroku Connect is not Heroku itself (Heroku Postgres), it’s the connector between Salesforce and Postgres databases that enables ‘Data synchronization’:
When to utilize Heroku Connect:
Here is an illustration of when you may have to utilize Heroku. During occasion advancements, a business needs to deliver an extraordinary application. They foresee the application will get a large number of downloads, yet they don’t need all that information in their Salesforce organization – they just need the features. You can utilize Heroku Connect to get that information for you along with sending refreshes from Salesforce. It takes into account high volume with low inactivity and high throughput.
Please click this link to read more about this topic.
