Accelerating Growth With System Integration: Part 3

[Music]

HOST: JIM HOLMAN: Hello everyone and welcome to Digital Journeys. Today we continue our discussion on the importance of system integration in part three of this series. We pick up where we left off with John Trader.

HOST: JIM HOLMAN: Thanks for joining me today, John. A question that comes up — you mentioned security. What security measures need to be considered to ensure that data is protected during integration?

GUEST: JOHN TRADER: A foundational measure of information security is protecting data in flight and data at rest. Any information transferring out of or into another system needs to be encrypted during transit and stored securely once it is in that system.

GUEST: JOHN TRADER: Information security is critical in system integration, especially when integrating externally with partners or customers. User access control and logging are essential to track what changed, who changed it, and when it changed.

GUEST: JOHN TRADER: The key is to ensure a high level of encryption and that data is secure between systems. You typically do not want to store data in the integration platform; data should be in transit between the source and the destination, not stored anywhere, especially critical data like PII or HIPAA-related information.

HOST: JIM HOLMAN: That's clear — you need a plan for protecting your data. Can you talk about potential risks involved and how those risks might be mitigated?

GUEST: JOHN TRADER: Historically, integrations were often at the database layer and batch processed. There needs to be a paradigm shift in the modern API era away from batch processing toward single-piece flow, also known as atomic transaction processing.

GUEST: JOHN TRADER: Integrating in real time for each specific transaction — for example, a sales order coming into your e-commerce platform integrating to your inventory and fulfillment system or ERP — reduces many issues. Batch processing can create problems where an error in the middle of a batch holds up subsequent transactions.

GUEST: JOHN TRADER: Moving to single-piece flow and leveraging APIs reduces unexpected delays and complexities. You only map the specific transaction and repeat that process many times, which simplifies error handling and recovery.

HOST: JIM HOLMAN: The paradigm shift needs to keep up with improving tools. Old-school database point-to-point batch processing probably needs to be rethought as tools modernize.

GUEST: JOHN TRADER: Exactly. The API layer allows business logic to stay within the systems that own the data, rather than pushing excessive business logic into the integration layer. Rules, cross-checks, and data integrity should be maintained within the source systems when integrating through APIs.

HOST: JIM HOLMAN: What timelines are typical for completing integrations, and what resources are needed by an organization that wants to complete an integration?

GUEST: JOHN TRADER: Timelines depend on the type of integration, the tools, and the approach. Using an integration platform as a service can speed up the process because there may be out-of-the-box connectors and faster mapping capabilities.

GUEST: JOHN TRADER: Complexity matters — is it a deep integration involving multiple services, or is it just customers and contacts? A typical integration project may range from three weeks to three months depending on complexity. You should identify a specific system of record as the source of truth and have that system send data to others that need it.

HOST: JIM HOLMAN: As platforms become less technical, do you find integrations are less developer-dependent?

GUEST: JOHN TRADER: Yes. No-code and low-code integrations can move faster with a smaller learning curve. Finding a person with specific integration skills can take time, so iPaaS tools and industry-specific integration tool sets reduce complexity and timelines.

HOST: JIM HOLMAN: We discussed needs that require integration to be moved into production quickly, so having less technical, more accessible integration options can help organizations scale developer capacity internally. One last question: How can the success of an integration be measured and what metrics should be considered?

GUEST: JOHN TRADER: Start with ROI and build a shared business case with the client. Integration investment often becomes critical when three, four, or five systems need to be connected, which can justify investing in an integration platform as a service.

GUEST: JOHN TRADER: Analyze current costs and what an automated system might look like. Common ROI opportunities include cost reduction by replacing legacy integrations, eliminating proprietary support, and reducing manual data entry that creates month-end pressure, errors, and extra managerial review.

GUEST: JOHN TRADER: Integration also reduces risk and can increase revenue by enabling faster processes, scalability, and market expansion. For example, integrating with marketplaces like Amazon, Walmart, or eBay can increase market presence and revenue without proportional increases in cost.

HOST: JIM HOLMAN: Thanks, John. We want to thank John Trader for joining me today to talk about system integration. It's been a lively and interesting discussion with many downstream benefits for customers of any size, from enterprise to startups and mid-market.

GUEST: JOHN TRADER: Thanks, Jim. I really enjoyed the conversation.

HOST: JIM HOLMAN: If you'd like to learn more about system integration and how it might benefit your organization, please contact us. If you enjoyed this discussion on system integration, please like and share on your favorite social media channels. Stay tuned for the next episode of Digital Journeys.