Salesforce is a goldmine of information about potential clients: names, addresses, contact information, licenses, even their favorite coffee order. Once you close the deal and the account is now a paying customer, it’s crucial that you get the information out of Salesforce and instantly spread it to the rest of your organization. In other words, you should event enable Salesforce.
Do it well and you enhance your initial customer experience with insights from the sales process.
Don’t do it well, and your newly minted customer must supply information you already know, or even worse, faces a delay while you onboard them.
These are the steps that the codelab will walk you through:
Your best bet: combine Solace and Boomi to create beautiful event-driven integration that distributes Salesforce information in real-time and lets you easily add on new functionality. I will talk about how to event enable Salesforce in a minute. But first, let’s talk about Tommy the Taxi Driver:
Tommy works for NYC Modern Taxi Company. Solace is following the journey of NYC Modern Taxi company, a traditional taxi company struggling to compete with ride sharing. Even though NYC Modern Taxi is completely made up (what, the name didn’t give it away?), they face many of the challenges I have encountered with customers.:
NYC Modern Taxi company uses Solace in combination with Boomi to address many different use cases, from IoT to analytics to SaaS integration. Today’s challenge: encouraging Tommy the Taxi Driver to use the brand-new NYC Modern Taxi ridesharing app.
After some discussion with the taxi cab psychologists, the business side of NYC Modern Taxi Company developed a 4-step strategy:
|Treat drivers like prospective clients: each driver is an “account” in Salesforce and has an assigned account rep
|Each account rep has an unlimited coffee budget with which to woo drivers
|Once the coffee does its job, the driver agrees to use the app.|
|As quickly as possible, the driver gets onboarded into the operations database|
The question now is: what’s the best way to make it work?
NYC Modern Taxi Company knows that Salesforce contains a wealth of information. But they are concerned about how to get the information out of Salesforce and across the enterprise.
The first method is what highly technical folks call the “annoying sibling technique” — constantly polling the Salesforce REST API to see if there’s been a recent update.
However, that solution means that one of the goals of the project won’t happen because polling consumes resources and slows down information movement.
While that isn’t ideal, NYC Modern Taxi might be willing to try it. But even after they pestered the information out of Salesforce, NYC Modern Taxi would still need to get the information to the right place at the right time. They could connect multiple microservices using REST. But then the other requirements become challenging because:
Point #2 is key because while version 1 has its scope locked in, imagine what version 2 could do:
Given the challenges involved, REST isn’t the right fit for NYC Modern Taxi. But what is the alternative to the annoying sibling/point-to-point architecture? The answer: event driven integration with Solace and Boomi.
Rather than using brittle, tightly coupled REST calls, Solace distributes events throughout NYC Modern Taxi, which means:
Using Boomi, things get even better:
Now that NYC Modern Taxi has a new architectural concept in mind (event-based integration), they’ve identified that determining where events are heading and what the content looks like can be a little difficult. Luckily, there is a solution. Solace PubSub+ Event Portal (or as some call it, the Google Maps of Microservices) discovers and presents the flow of events in a visual form.
Using the Event Portal, NYC Modern Taxi can map out how events flow through the enterprise and design what the schemas and topic strings will look like. That shared knowledge is important during the design phase of a project, but it’s also key during the implementation phase as well. You’ll see how Event Portal helps in that regard a little later.
Before NYC Modern Taxi can be fully-event driven, they need to get events out of Salesforce.
The magic starts with triggers. Within Salesforce, every change to an account (including the ones for Tommy and other drivers) can fire a trigger written in a language called Apex.
Platform Events is an internal message bus that comes with Salesforce. It lets both internal and external applications listen for events. It’s not the most flexible event broker, it’s only focused on Salesforce events, but it gets the job done. It also has a snazzy logo that looks like an antenna. And it just so happens that Boomi has a built-in connector that brings Platform Events out of Salesforce and into NYC Modern Taxi’s integration stack.
Now the implementation is getting somewhere! The next logical step is to intelligently distribute the information from Salesforce to other interested applications. Enter Solace. The Solace PubSub+ Connector for Boomi can help with:
From there, the event can go to any application within NYC Modern Taxi. Adding in more applications and devices is as simple as adding a subscription to get the information flow going. Mobile applications, data lakes, Instagram accounts, and more can be added without disturbing the existing code.
Now NYC Taxi has an enterprise architecture and knows how events will get from Salesforce into the target system. The only thing left to do is create it.
Luckily, NYC Modern Taxi has a giant head start on implementation. When developers start building solutions in Boomi, the PubSub+ Connector gives them access to the architect-defined schemas and topics previously defined in the design phase in the PubSub+ Event Portal. No more guessing about what the data looks like, or which topic to subscribe to. It’s all at your fingertips.
Reading about the implementation is one thing, getting to see Tommy’s Salesforce data speed through NYC Modern Taxi in real-time is a whole ‘nother enchilada. Check out the CodeLab for this post: you’ll get free access to Boomi, Solace, and Salesforce and get to see the solution in action. Extra credit if you can connect it to Instagram!
These are the steps that the codelab will walk you through:
We’d love to hear your feedback in our Solace Developer Community. Even better, showcase your solution there to share it with the community!
As an architect in Solace’s Office of the CTO, Jesse works helps organizations of all kinds design integration systems that take advantage of on event-driven architecture and microservices to delivery amazing performance, robustness, and scalability. Prior to his tenure with Solace, Jesse was an independent consultant who helped companies design application infrastructure and middleware systems around IBM products like MQ, WebSphere, DataPower Gateway, Application Connect Enterprise and Transformation Extender.
Jesse holds a BA from Hope College and a masters from the University of Michigan, and has achieved certification with both Boomi and Mulesoft technologies. When he’s not designing the fastest, most robust, most scalable enterprise computing systems in the world, Jesse enjoys playing hockey, skiing and swimming.[position] => [url] => https://solace.com/blog/author/jessemenning/ ) )