The document discusses how APIs can improve enterprise application integration by focusing on the frontend experience rather than the backend. APIs allow for faster iteration cycles and easier integration of multiple backend systems. They also enable real-time access to data and events across systems for both internal employees and customers through mobile apps. By exposing system events through APIs and evaluating which events are most relevant, organizations can build personalized notifications and streams of important updates.

1. Proprietary and Confidential
We Make Work Software Work™
1
At the Glass Integration with APIs
Peter Yared, Founder & CTO

2. Proprietary and Confidential ©2015 Apigee Corp. All Rights Reserved.
The views expressed in this presentation are those of
the presenter, and not necessarily those of Apigee
Corporation or the presenter’s employer.
2

3. Proprietary and Confidential
Enterprise Application Integration is Painful
๏Lots of backend work
๏Extremely time
consuming
๏Low time to value
๏ETL and messaging
rather than APIs

4. Proprietary and Confidential
EAI is Systems Centered,
Rather than Human Centered
๏Focus on backend
rather than frontend
๏IT disconnected from
end users
๏Long iteration cycles

5. Proprietary and Confidential
EAI Doesn’t Keep up with the Business
๏Systems are never
fully integrated
๏And then another
merger/acquisition
happens
๏Continual “groundhog
day”

6. Proprietary and Confidential
Software Delivery has Changed,
But It’s Pretty Much The Same
6
Siebel CRM 1999 Salesforce CRM TODAY!

7. Proprietary and Confidential
Because Software is Designed
for the Daily User, not Everyone Else
7
Designed for the 99%
Designed for the 1%

8. Proprietary and Confidential
APIs Can Unbundle Software for the 99%
๏Use APIs to integrate
multiple backend
systems
๏Focus on the frontend
rather than the
backend
๏Deliver user delight
๏Iterate quickly!

9. Proprietary and Confidential
Especially When Skinning Old Systems

10. Proprietary and Confidential
What’s Changing?
10
Mobility Notifications Predictive Push Computing

11. Proprietary and Confidential
Inverting Enterprise Software Workflows
11
Deep enterprise event Call to actionDistilled detailPersonalized notification

12. Proprietary and Confidential
Picture at a Real Customer
12

13. Proprietary and Confidential
Their Execs Walk Stores w/ Binders

14. Proprietary and Confidential
APIs Allow Access to Data

15. Proprietary and Confidential
For Everyone

16. Proprietary and Confidential
Even Floor Associates

17. Proprietary and Confidential
For Mobile, APIs Need to Deliver Push

18. Proprietary and Confidential
Architectural Shift to Push
18
✴ Pull
✴ Database server
✴ User initiates query
✴ No caching
✴ Decoupled tooling
✴ Lots of pulls
✴ Web application server
✴ User initiates query
✴ Lightweight caching
✴ No integrated tooling
✴ Push
✴ Mobile+Web App server
✴ User receives interesting events
✴ Profile of user, history and usage
✴ Integrated tools focus stack
Client Server
80’s & 90s
Web Clients
90s, 00s, & 10s
Push
Today & Future

19. Proprietary and Confidential
Example – Feed Approvals from Multiple
Systems into a Stream

20. Proprietary and Confidential
APIs Can Expose All of these Events
Most internal system events are
tucked away in big data and legacy
systems
๏Unstructured Data Stores
๏Supply Chain/Logistics
๏Financials
๏Human Resources
๏Legal
๏IT
๏Customer Detail

21. Proprietary and Confidential
APIs can Expose the Events
Ambient Events
• Weather
• Traffic
• Emergencies
External System
Events
• Stock Movements
• News Events
Internal System
Events
• Deal Teams
• Customer Actions
• Tickets Filed

22. Proprietary and Confidential
The Events are Typically Well Bounded
• Most systems have
discrete, identifiable events
๏ Lost opportunity
๏ Currency shift
๏ Case closed
๏ Order shipped
• Distributable by rules-
based triggers

23. Proprietary and Confidential
Once the API Exposes the Event, How is it
Processed?
Commonality
of Interest
Level of
Event
Enterprise
Events

24. Proprietary and Confidential
Commonality
of Interest
Level of
Event
Enterprise
Events
First the API has to Expose the Event
๏ Trap enterprise events as they occur
๏ Cache values and compare in order to provide history
๏ Measures deltas in values

25. Proprietary and Confidential
Commonality
of Interest
Level of
Event
Enterprise
Events
Then the API has to Evaluate If the Level is
Material
๏ Measure level of event
๏ Learn level of event that is of interest to organization and parts or organization
๏ Only propagate events that are of interest

26. Proprietary and Confidential
Commonality
of Interest
Level of
Event
Enterprise
Events
Then the API has to Figure out Who It’s
Interesting To
๏ Observe user data consumption and activity with counts
๏ Build organizational graph of interest in events
๏ Observe immediacy of interaction
๏ Observe graph of interaction (email headers and other mechanisms)

27. Proprietary and Confidential
Building the Organizational Graph
27
Human Resources
System
Email Clustering
Usage Patterns
Dynamic Graph of Employees:
Roles,Projects,Interest LevelinEventsData Accessed

28. Proprietary and Confidential
Integration at the Gorilla Glass
๏Use APIs to integrate
multiple backend
systems
๏Focus on the frontend
rather than the
backend
๏Deliver user delight
๏Iterate quickly!

29. Proprietary and Confidential
Stuff to Add
๏ Rosetta Stone – what is a customer ID on 4 different systems