Latest questions:
Trending questions:
Hot questions:
Truth of integrating SaaS Platforms
Context: Integrating a chosen Sales & Marketing SaaS Platform with in-house systems is where rubber hit the road. There are basically two options Build vs Buy. Build – Create custom, hand-coded, point-to-point integrations between the APIs of both applications. Buy iPaaS – Use a cloud-based integration platform to create custom integrations using the hub and spoke structure of the platform, a marketplace of pre-built connectors that expose application meta data, and graphical design tools.
Questions:
1) Can you highlight a challenge you faced in integrating Sales & Marketing SaaS Platform with other in-house systems?
2) What are the pros and cons of “Buy vs. Build” decision?
70 months ago
2 answers
Integrations are always challenging. I agree with you integrating SaaS platform with in-house platform brings more challenges in terms of architecture, security and application design.
I assume you are integrating your home grown application to SaaS through REST or SOAP kind of service layer. Some of our challenge -
- Enterprise Security ( Firewall , Caching etc)
- No control on SaaS APIs ( If they change structure, we are going to have a direct impact)
- Platform knowledge - some kind of knowledge/ training required to developers of this SaaS platform.
However, number 2 and 3 are true for integrations within the same enterprise home grown platforms as well.
63 months ago
SaaS
Software as a service is a software licensing and delivery model in which software is licensed on a subscription basis and is centrally hosted. It is sometimes referred to as "on-demand software".
SaaS is typically accessed by users using a thin client via a web browser.
63 months ago
