In this course, you’ll learn about the concepts, options, and challenges integrating Salesforce with other systems. The materials for this course are available at: https://github.com/the1mattkaufman/salesforce-integration-on-a-budget
Play by Play is a series in which top technologists work through a problem in real time, unrehearsed, and unscripted. In this course, Play by Play: Salesforce Integration on A Budget, Matt Kaufman and Don Robins demonstrate how to design and build a Salesforce integration with no budget, limited time, and differing capabilities on each external system. Learn about valuable insight around best practices for selecting the right tool for the integration task at hand, how to work around integration limitations that you might encounter with legacy systems, and building Apex REST and SOAP web services and consuming WSDLs. By the end of this course, you’ll have a solid perspective of the many integration approaches available for your next integration project on a budget. The materials for this course are available at: https://github.com/the1mattkaufman/salesforce-integration-on-a-budget
Don Robins is a well known Salesforce MVP, instructor, author, and speaker.
A custom business application developer for more decades than he cares to
admit, he focuses on Salesforce technical instruction and knowledge
Course Overview Welcome to this Salesforce Play by Play with Pluralsight. Salesforce Play by Play is an interactive series where we sit down with Salesforce experts such as MVPs, consultants, developers, and architects to discuss common challenges faced every day by Salesforce customers. We'll be learning while discussing concepts and debating tradeoffs on various approaches to solving real-world problems. We learn by reviewing system configurations or writing code and then exploring the benefits of any particular solution. In this course we challenge Matt Kaufman, chief technology officer for MK Partners, to explain how he would design and build a Salesforce integration with no budget, limited time, and differing capabilities on each external system. First, Matt walks us through an inventory of both business and technical questions to explore with stakeholders to get a true understanding of the requirements for any integration project. He explain many of the options, integration features, and mechanisms built into the Salesforce platform, and he discusses challenges around choosing and selecting from the many security standards available to any customer. Next you'll watch as he demonstrates various integration approaches available for his sample integration scenario, including how Salesforce can respond to web hooks sent by an external system leveraging an unauthenticated Salesforce site as an end point. Along the way he clarifies general integration terminology and concepts, explores building Apex REST and SOAP web services, and consuming WSDLs, and shows some of the advantages of using JSON versus XML for data payloads. We'll also discuss call out patterns, securing outbound SOAP calls, and dealing with undocumented APIs. By the time we're done you'll have gained some valuable insights around best practices for selecting the right tool for the integration task at hand, learned how to work around some integration limitations that you might encounter with legacy systems, and you'll have some great perspective of the many integration approaches available for your next integration project. So, please join us for Salesforce Integration on a Budget, we hope you enjoy it.
Conclusion So that's a lot. You have a lot of options. So let's recap. Just sort of going back over what have we talked about, what have we accomplished here? So we've looked at the different players involved with integration, we talked about webhooks, callouts, web services, and also ETL tools. We touched on some other aspects too, like email services, but the major players are those four. And that's really where you're going to start is figuring out which of those tools is right. The tricky part is figuring out which is right, and there's not always a right answer, sometimes you have multiple options, and so now you're going to base it on what are you most familiar with, what fits your budget, what fits your timeframe from the project. There's not one answer. Same thing with the security. There's not one standard, there are a lot of different standards, so you have a lot of options. The tricky part is figuring out which option you're going to go with. Right, and figuring out what it's going to cost and basically what you have available to you in the systems that you're trying to integrate with. And things are changing all the time. So new standards come out, new features come out, new APIs come out, and that means that something you built two years ago you might be able to do better today. We didn't talk about platform events, but it's a fairly, as of winter '18, it was a fairly new edition into Salesforce, but I know that that's a new asynchronous integration for, integration mechanism, and where there's going to be more, there's no doubt. But it's exciting, and so we're always learning new ways of connecting systems and being more efficient, we don't have to keep doing it the same way using these ETL tools that run at night, and as a result of those new ways we get better performance, our business processes run more efficiently, we get real-time data, less duplicate data entry, things like that. Sounds like the constant is you've got to think about it. You've got to think about it, and design it intelligently, and then figure out which way to go and then just go there. Yep. Well thank you very much, Matt. And thank you, and we'll see you next time.