Why we should go with Integration Hub for integration rather than REST Message?

[Priya Singh 2 2]

Hello Team,

I have got one requirement to do integration between 2 service now instances and both organizations having Integration Hub licenses, my question is that which is the best practice for this integration REST Message/Scripted REST API or Integration HUB.

As per requirement they want this integration between Incident, Request, Case.

Also please provide pros and cons of both methods. 

[Harish Bainsla]

https://www.servicenow.com/community/developer-forum/need-advice-on-integration-using-rest-api-best-...

https://docs.servicenow.com/bundle/tokyo-application-development/page/app-store/good_practices/scrip...

[Amit Gujarathi]

HI @Priya Singh 2 2 ,
I trust you are doing great.

REST Message/Scripted REST API:

Pros:

• Flexibility: Offers a high degree of flexibility in terms of customization. You can tailor the integration to fit specific needs.
• Granularity: Allows for fine-grained control over the data being sent and received.
• Widely Used: This method has been in use for a long time, so there's a wealth of knowledge and best practices available in the community.
• Direct Integration: Provides a direct way to communicate with external systems without the need for intermediary processes.

Cons:

• Complexity: Requires a deeper understanding of both the source and target systems, as well as the intricacies of RESTful services.
• Maintenance: As business needs evolve, the custom scripts might need frequent updates, which can increase maintenance overhead.
• Error Handling: Requires robust error handling to be built into the scripts to ensure smooth integration.

2. Integration Hub:

Pros:

• Simplicity: Provides a no/low-code approach to integration, making it easier to set up and maintain.
• Pre-built Spokes: Comes with a variety of pre-built spokes for common integrations, reducing the need for custom development.
• Flow Designer: Allows for the creation of integration flows using a visual interface, making it more user-friendly.
• Error Handling: Built-in error handling mechanisms can simplify the process of managing and resolving integration issues.
• Scalability: Designed to handle a large number of integrations efficiently.

Cons:

• Less Flexibility: While it simplifies the integration process, it might not offer the same level of granularity and customization as direct REST integrations.
• Licensing Costs: Integration Hub requires separate licensing, which can increase costs.
• Learning Curve: If you're new to Integration Hub, there might be an initial learning curve to understand its features and capabilities.

Recommendation:

For integrating between Incident, Request, and Case modules across two ServiceNow instances, Integration Hub would be the recommended approach, especially if both organizations have licenses. It provides a more streamlined, maintainable, and scalable solution. However, if there are very specific and complex requirements that cannot be achieved using Integration Hub, then REST Message/Scripted REST API would be the way to go.