How cloud-based integration platform as a service can be used for speeding up time-to-market and addressing a wider range of customers. Based on a case study.
1 of 17
More Related Content
How to Use iPaaS to Scale Your Business - Case Study
1. How to Use iPaaS to Scale
Your Business
- Case Study -
Building out a full-service integration hub for
eCommerce-related software products
2. Meet Infinite Codeworks
| System integration
experts based in the UK
| Specialized in Channel
Advisor, Sage, Shopify,
Shopware and other
eCommerce-related
business apps
| 7 years of customer-
centric system
integration projects
3. Labour-intensive business
| The system integration business is a crowded
space these days
| One way to stay competitive is to reduce time-to-
market of individual integration projects, and to
be able to do more in less time
| This, however, requires a considerably higher level
of standardization of integration processes – even
for the projects that are very similar to each other
4. Labour-intensive business
“We realized that the majority of
our customers shared a core
business logic [...]
The problem was that we were
able to carry out such projects only
as point-to-point integrations.”
- Ben Burch,
Managing Director of Infinitie Codeworks
5. Standardizing integration
| To have more standardization in their integration
processes, Infinite Codeworks decided to build a
series of integration templates, or connectors
| These connectors were supposed to help them map
common business logic to create ready-to-use
integration recipes for most widespread scenarios
| For clients‘specific requirements, the out-of-the-box
recipes will be adapted accordingly, allowing for
much more efficiency
6. Main Challenges
| Integrated systems should not be connected to
each other – an extra integration layer needed to
be built
| Infinite Codeworks has limited development
resources: Working on such a layer would have
taken a toll on the core business
“Our business is all about delivering the right
solution to our clients, that is what we focus on.”
- Ben Burch
7. Specific Requirements
| The integration layer should:
{ Enable disconnected input and output
{ Ensure reusability of integration components
{ Offer different ways to collect data: polling,
fetching; via API and webhooks; etc.
{ Have an API of its own
8. Solution: elastic.io iPaaS
| Integration Management API
| Reusable connectors
| SDKs for custom connectors
| Intuitive mapper
| Easy-to-follow monitoring
and error-handling
9. Solution: elastic.io iPaaS
“When I saw during the demo how
elastic.io works, I realized that it literally
was the part of system that we had been
planning to build ourselves.
It had all the things we have thought of,
and it was just there, ready as a platform
rather than us building it from scratch.”
- Ben Burch
10. Connectors and hub
| Infinite Codeworks migrated their existing code to
the platform, rewriting PHP into Node.js
| The elastic.io platform is now used as a uniform
integration layer for all their integration projects
| Available connectors have been adopted and
modified according to specific requirements
| New connectors are created with the Node.js-
based SDK
13. Behind the Scenes
| One infrastructure for all integrations _ Reduced
development time by a factor of 10
| Built-in tools for testing and debugging new
connectors on the go
| Built-in comprehensive monitoring and logging of
integration flows across all integrated systems
14. Focus on the core business
“Working with the elastic.io platform, we
are able to focus on our clients‘ business
and extend the functionality of the
platform with specific customizations.
I liken it to using cloud servers vs. building
and configuring your own hardware: Sure,
we can do it – but should we?”
- Ben Burch
15. Benefits
| Closer focus on adding value for the clients
| Faster project implementation while keeping the
integration costs low
| Addressing a broader client segment
| Speeding up time to market
| Gaining new revenue streams
16. Infinite Codeworks: Full Case Study
For more details,
read the full case study,
accessible under:
http://go2.elastic.io/infinite