Salesforce continues to grow at a 30% rate year-over-year. As a result, our data silos continue to increase across the company. This is especially true when companies are acquired and incorporated into the overall Salesforce ecosystem. In order to continue to support a $20B dollar company by the year 2020, our internal data integration infrastructure and architecture will need to be modernized to support the volume of business needs while curbing operating expenses. Our vision is to connect the business to data that they can trust, when and where they need it, so that the enterprise can continue to scale and innovate. This document describe in detail how this will be achieved.
Salesforce has been growing at 30% year over year. In order to grow at this rate while supporting the business, IT has had to make compromises. Many of these compromises have been to defer infrastructure and architectural investments to a later date. Unfortunately, over time, IT will become the bottleneck or worse, the blocker for the company to deliver services to our customers. The diagram below depicts a representation of the current state of the P2P integrations within Salesforce. Unfortunately, at the time of the post, this is the internal infrastructure that the company relies on to run a multi-billion dollar a year business.
The purpose of this document is to help guide and inform IT project teams to the correct integration platform for projects. Note that this is only a guide, as there can be multiple options based on the integration activities. Use the matrix in this document in conjunction with input from the Enterprise Architecture Review Board (EARB) to select the appropriate technology.
Not long ago I presented at the MuleSoft TopMule Meetup ’14 in San Diego, CA, on an initiative I’m running at salesforce.com called Free The Data: Transforming The Way The Business Connects To Data. With approximately 400 MuleSoft employees in attendance, MuleSoft has doubled its size in just one year. It’s a testament to the industry demand for their integration and API solutions. My talk centered around how we are aggregating, exposing and simplifying access to internal enterprise data.
Today many IT departments have a hybrid of legacy on-premise applications and newer, more innovative Software-as-a-Service (SaaS) business applications that they need to manage. Salesforce.com is no different; we have a lot of SaaS and on-premise applications that we use to run our daily operations. Our Enterprise Application Integration program has a number of use cases that we support, but can be consolidated into two main concentration areas: 1) System-to-System Data Exchange, and 2) API Data Access.
To consistently ensure high data quality, you need to create a data quality culture. The key to implementing a data quality culture is to focus on the right things at the right time. Initially, it’s all about user adoption. Over time you need to understand usage trends, adopt standards, and then train on common best practices.
Over the course of 14 years, salesforce.com has grown at an extremely rapid pace. It has taken salesforce.com 12 years to reach $2B in annual revenue. In comparison, it took Microsoft 16 years, Oracle 17 years, and SAP 23 years to reach this same milestone. As with any high-growth and fast-paced company, the focus for internal based integrations is on near term delivery. Teams work at a whirlwind pace to satisfy business requirements and move the business forward. Unfortunately over time, this can lead the teams to focus on delivering point-to-point integrations rather than designing loosely coupled integrations. This ultimately results in a complex structure that is not only difficult to maintain but costly too.