Integrating with the Internet of Things

Integrating with the Internet of Things

In this article I talk about some integration patterns that can be used when wanting to integrate multiple devices with Salesforce. Imagine the scenario where we are a fitness tracker manufacturer and we want to communicate real-time or near-real-time updates from a fitness device through to Salesforce. Typically this would be challenging due to the issues of LDV (Large Data Volume) and the Salesforce Inbound API limits which would make it near impossible to build a solution making calls into a Salesforce org. Despite these large challenges, there are still patterns we can adopt and use to make this form of use case work, and drive automations from the Salesforce platform. Lets work through a few examples and I will detail out the architectures that can be used to make it work.


Scenario 1 - Connected Fridges


We are a company that manufactures smart fridges. We want to be able to send real-time alerts and notifications to customers whenever the fridge sensor detects a fault or a reduction in temperature. We can approach this with the following architecture in Salesforce:

Salesforce Org: Our main Salesforce Org which is owned and run by the Fridge Company. This would be the global CRM containing Fridge and Customer Data

Heroku Backend Service: A Heroku Backend service hosting REST APIs that the worldwide fridges are allowed to call in to

Heroku Connect: To synchronise data between Salesforce and Heroku and invoke the creation of Platform Events

  1. An event occurs in the Smart Fridge which picks up on a sudden rise in the safe temperature in the fridge.
  2. Using a REST API, the Smart Fridge sends a notification to the Fridge Back-End service which is hosted on Heroku. Each fridge communicates with an API hosted on Heroku which is built to take notifications from global fridges.
  3. The Heroku Service creates and saves a new Platform Event record.
  4. Heroku Connect synchronizes this platform event to Salesforce.
  5. In Salesforce we fire a Process Builder or IOT Orchestration based on the Platform Event. 
  6. The Platform event could then trigger a chatter post, email notification or invoke a push notification or SMS via a trigger ensuring that the user gets alerted on their mobile devide of a temperature rise event.


Now the obvious question that can be raised here is when you have over a million fridges distributed worldwide, would this not breach Salesforce API limits. It would, however since we are using Heroku Connect, Platform Event records that are raised via Heroku Connect do not count towards the inbound API call limit in Salesforce. As a result we are able to use this architectural approach and stay inside of Salesforce platform limits.


Scenario 2 - Trucks, Shipments and GPS Coordinates


Trucks need to send their GPS co-ordinates every minute into the application. Shipments which are going to be late, should be notified to the customer. We can adopt the following architecture for this scenario



In the above example we are leveraging an ESB whch will front an API that trucks can submit their real-time coordinates to. These can be written to a backend service. A batch process in the back-end service will run every 5 minutes looking for all late running shipments and use the ESB to send an API call into Salesforce to update the Shipment records. This will flow as follows

  1. Truck sends a message to the ESB with it’s co-ordinates
  2. ESB writes the coordinates to the Data Warehouse
  3. Custom Node.js application runs a scheduled process every 10 minutes, which calculates if a Shipment may be late based on GPS data.
  4. Node.js application makes a call into the ESB to update the Shipment statuses
  5. ESB make a Remote Call In to Salesforce via the SOAP API to update the status on the Shipment records.
The above scenarios cover example where we want to be able to make real-time calls into the Salesforce platform from multiple devices in real-time, yet want to follow a pattern that keeps us within the API governor limits. It's useful to keep these approaches in mind for the CTA exam when considering integration ideas.

Comments

  1. My own world9 April 2021 at 05:23

    Thanks Mitesh for a nice guidance article! can we not fit in Heroku also in Scenario 2?

    ReplyDelete

Post a Comment

Popular posts from this blog

Salesforce Integration Approaches

Image
Salesforce Integration Approaches Most if not all enterprise Salesforce projects involve an element of integration. In this article I have summarised 3 common integration use cases that come up and an optimal approach for solving those use cases. This is useful for the CTA exam when certain scenarios come up and you have to consider possible approaches that can be used to solve them. Pattern 1 - Remote Process Invocation - Request Reply Scenario  In this scenario we want to make a callout from Salesforce to a Remote System and receive an immediate response. For example, we want to make a callout from Salesforce to SAP to check on Stock for a particular Product chosen on a Salesforce opportunity. We want the stock check results to be displayed in real time.  Approach Create a Lightning Component which has an Apex Controller that can make a REST or SOAP callout to an external service. Create a button on the Lightning Component to invoke the callout method in...
Read more

CTA Study Planning

Image
So you've made the gigantic decision to go forward and prepare to become a Salesforce CTA. Well done! Taking the effort to formalize your architecture experience with the Salesforce CTA badge of honour, is a great hallmark to achieve in the Salesforce ecosystem and it is great to have the courage to take part in the journey. As I always say, the journey is more important than the outcome, because it is the learnings from the process that you will apply day to day in your job, and necessarily the CTA stamp itself. So lets have a look at what a CTA journey typically can look like: Step 1 - Salesforce Domains Pre Study Step 1 involves going through each of the materials which are listed on the Salesforce Architects Trailhead site, and taking the time to meticously go through each article in detail. This is the fundamental wisdom that will build your Salesforce base, and to be a better architect your baseline must be strong. I spent a lot of time reading the articles here. Sometimes we...
Read more

The Evolution of Salesforce Implementation

Image
How Implementing Salesforce has Evolved Little bit about me I started my Salesforce career in 2009, working as a Graduate for Deloitte on a large Salesforce Customer Portal implementation for a media client in London. Having worked through multiple roles from developer through to Program Architect I have had a chance to see the growth and evolution of the Salesforce platform. In 2018 I obtained the elusive Salesforce Certified Technical Architect qualification, the topmost credential in the Salesforce ecosystem and am now the Head of Architecture for a global Salesforce Silver Consulting Partner, VRP Consulting, helping our enterprise clients innovate on the platform. In this article I will be talking about how the platform has evolved and how some of its newest features are transforming the way Salesforce is implemented. How things began Back in 2009, the declarative options were more limited and required the use of APEX code to deliver any form of cus...
Read more