For most organizations today, integration is being solved with “point-to-point” solutions that spiderweb between apps and services. This is simply an extension of legacy enterprise integration patterns we’ve seen for 2 decades. But with modern enterprise using 100s of applications, this point-to-point model doesn’t scale. By focusing on the data you care about - rather than the interfaces of your applications - integration architecture is able to scale, while simultaneously creating a data governance and mediation layer.

1. Cloud Elements 2017 - Confidential & Proprietary
SUCK LESS
Putting Data at the Center of integration strategy

2. Ross Garrett .
Head of Product Marketing
Cloud Elements
Hello! My name is…

3. Cloud Elements 2017 - Confidential & Proprietary
BAD NEWS...

4. flawed

6. Cloud Elements 2017 - Confidential & Proprietary
ISLANDS OF DATA ARE MULTIPLYING

7. Cloud Elements 2017 - Confidential & Proprietary
MASSIVE GROWTH
OF PUBLIC APIs
757% .
Increase in Web APIs
January 2010 - January 2016

8. Cloud Elements 2017 - Confidential & Proprietary
ENTERPRISE IT
The average Enterprise has
more than 1,071 internal cloud
services.
Getting every app to work
together is a major need.

9. Cloud Elements 2017 - Confidential & Proprietary
Authenticate Discover
Custom Objects
Map &TransformEvents &
Polling
Workflows
CONNECTING
TO THE API
BulkError
Handling
INTEGRATING
WITH THE API

10. ORGANIZATIONS TIME
Integrating and consuming a vast array of APIs … and
it’s getting exponentially worse!

11. Cloud Elements 2017 - Confidential & Proprietary

12. Cloud Elements 2017 - Confidential & Proprietary
“WHERE

13. Cloud Elements 2017 - Confidential & Proprietary
- INTERFACES AND APPS
- Point-to-point
- This can only scale to 5-6 large apps
- RATHER THAN DATA
- One-to-many
- Using common data models integrating to all apps

14. ESB
iPaaS

15. Cloud Elements 2017 - Confidential & Proprietary
How can you expect every user or
developer to be experts across a vast
array of applications?
What if the most important thing in your
integration changes: The data model

16. Cloud Elements 2017 - Confidential & Proprietary
APIs
LET’S
THINK
ABOUT
APIs

17. Cloud Elements 2017 - Confidential & Proprietary
Dynamics CRM {Contact}
Salesforce CRM {Contact}

18. Cloud Elements 2017 - Confidential & Proprietary

19. Cloud Elements 2017 - Confidential & Proprietary
SugarCRM
Netsuite
Hubspot
Dynamics
SFDC

20. FOCUS ON THE
YOUR data inside each app is where
all the value lies

21. INVOICE
DATA MODEL

22. Cloud Elements 2017 - Confidential & Proprietary
REDEFINING THE APPROACH TO
INTEGRATION
CLOUD ELEMENTS UNIFIES THE
WORLD OF APIs
ALLOWING YOU TO FOCUS ON
THE DATA YOU CARE ABOUT

23. Cloud Elements 2017 - Confidential & Proprietary
REDEFINED
UNIFY APP INTEGRATION
USING NORMALIZED APIs
FOCUS ON YOUR DATA
USING COMMON MODELS

24. Cloud Elements 2017 - Confidential & Proprietary
CONTENTMEMBERS SUPPORT
INSPIRATO
Multiple Apps Working Together to Create Something New
RESERVATIONSBUDGET

25. Cloud Elements 2017 - Confidential & Proprietary
CONTENTMEMBERS SUPPORT
INSPIRATO
Multiple Apps Working Together to Create Something New
BUDGET
POST /photosGET /customer GET /ticket PATCH /residencePUT /order
RESERVATIONS

26. Cloud Elements 2017 - Confidential & Proprietary
UNIFIED APIs
MS DYNAMICS (SDK) API
SALESFORCE (REST) API
NETSUITE (SOAP) API
// create an Account object and set the body
Account accountClass = new ApexClass();
apexClass.Body = classBody;
Account[] classes = { accountClass};
// call create() to add the class
SaveResult[] saveResults = sforce.create(classes);
for (int i = 0; i < saveResults.Length; i++)if
(saveResults[i].success ) Console.WriteLine("Successfully
created Class: " saveResults[i].id);}
<EntityType Name="account" BaseType="mscrm.
crmbaseentity"> <Key>
<PropertyRef Name="accountid" />
</Key><!--Properties and navigation
properties remoevd for brevity -- >
<Annotation Term=” Org. OData.Core.V2.
Descriptio” String=’Business that represents a
customer or potential customer. “ /> <Entitiy
Type>
<?php require_once
'./PHPToolkit/NetSuiteService.php';
$service = new NetSuiteService();
// create Customer record $customer1 = new
Customer();$name = 'customer_php_async_1';
$customerFields1 = array (
'entityId' => $name, ‘companyName =>
$name, ‘externalId’ => $name) ;
NORMALIZATION OF BACK-END APIs
SIMPLIFIES INTEGRATION
UNIFORM REST API

27. NORMALIZED APIs & ERROR HANDLING
AUTHENTICATION
DISCOVERY APIs & CUSTOM DATA
EVENTING & BULK
ELEMENT MODEL SCHEMAS
OPENAPI SPEC
OUR “ELEMENTS”
PAGINATION & SEARCH

28. Cloud Elements 2017 - Confidential & Proprietary
YOUR DATA MODELLING
Company
1. Reusable Data Resources -
exposed as APIs
2. Delivering “on-demand”
representation of data
3. Accessing only the data you care
about
DATA MODEL

29. Cloud Elements 2017 - Confidential & Proprietary
ELEMENTS CATALOG

30. Cloud Elements 2017 - Confidential & Proprietary
ELEMENT &
HUB BUILDER
PLATFORM.
Custom Data UsageEvent Bulk
COMMON RESOURCE TRANSFORMATIONS FORMULAS
Search
Uniform
APIAuthentication
Platform UIPlatform APIs Elements Connect
GROUND2CLOUD

31. Cloud Elements 2017 - Confidential & Proprietary
Build Integration with
Low Code UI
● Elements
Feature rich connectors to any
platform (back-office or SaaS)
● Common Data Models
User-defined data APIs to simplify
integration
● Formulas
Reusable workflows, which can be
exposed via APIs

32. Cloud Elements 2017 - Confidential & Proprietary
Deploy Integration with
No Code UI
● Formulas
Workflows are packaged and ready for
1-Click activation
● Default Data Mapping
Default data mapping, that can be
extended or edited on demand
● Elements
Users select the endpoints they need
and authenticate via the provider

33. Cloud Elements 2017 - Confidential & Proprietary
Embrace the convergence of application
and data integration, ensuring
consistency and governance
Focus on the Data
you care about

34. Cloud Elements 2017 - Confidential & Proprietary

35. Ross Garrett
Head of Product Marketing
Cloud Elements
Questions?