Today we’re going to take a look at how traditional or even de facto standards for integration aren’t always the best choice for web mobile and IoT applications. The standard I’m talking about is of course HTTP and ever popular REST APIs. While I won’t be so bold as to disregard this integration pattern entirely, I do want us to take a critical look at how and where integration can be improved – by understanding the limitations of today’s app integration technologies and considering the business factors that impact success in the attention economy.

2. The Attention Economy and
the Internet
@gssor
Ross Garrett
rgarrett@pushtechnology.com
A critical look at integration strategy
when the network is working against
you

3. Copyright Push Technology 2016
Attention Economics
“…in an information-rich world… a wealth of
information creates a poverty of attention…”
(Simon 1971, pp. 40–41)
3

4. Copyright Push Technology 2016
Attention economy and the net
4

5. And there’s no shortage of information…

6. Thinking about attention in the
context of data and applications

7. Data – It’s about time

8. Copyright Push Technology 2016
Performance alone has huge business impact
Roger Dooley – Forbes.com
http://www.forbes.com/sites/rogerdooley/2012/12/04/fast-sites/
8

9. Copyright Push Technology 2016
Mobile & IoT Apps MUST consider the network
http://blog.loadimpact.com/blog/mobile-network-emulation-the-key-to-realistic-mobile-performance-testing-feature-release/
9

10. Copyright Push Technology 2016
You can’t assume unlimited bandwidth
10
http://nordicapis.com/optimizing-apis-for-mobile-apps/

11. Copyright Push Technology 2016
Avoid “Buffer Face”
11

12. So why might HTTP be a poor
choice for mobile & IoT
integration?

13. Copyright Push Technology 2016
“Applications created today using old traditional
architecture will be business-constraining legacy before
they are completed.”
Yefim Natis
Gartner
Analyst View
And Attention-
Constraining!

14. Copyright Push Technology 2016
RESTful APIs are the de facto integration standard today
14

15. Copyright Push Technology 2016
JSON Data
{
uid : 1234567890,
title : “Something”,
db_key : “some_thing_item”,
modified_date : “13-06-1991”,
…
}

16. Copyright Push Technology 2016
JSON Data Redundancy
It’s like the internet is running with Debug turned on
{
uid : 1234567890,
title : “Something else”,
db_key : “some_thing_item”,
modified_date : “06-08-2015”,
…
}

17. Copyright Push Technology 2016
HTTP Request / Response
17
{
route-id : 54321,
route : “WAT-WOK-17:18,
route-details : [
{ station : “waterloo”,
etd : “17:18” } ,
{ station : “clapham”,
etd : “17:28” } ,
{ station : “woking”,
etd : “17:38” } ,
}
Get Request
Return JSON Document
{
route-id : 54321,
route : “WAT-WOK-17:18,
route-details : [
{ station : “waterloo”,
etd : “17:18” } ,
{ station : “clapham”,
etd : “17:28” } ,
{ station : “woking”,
etd : “17:38” } ,
}
149 characters sent
Backend System Client App

18. Copyright Push Technology 2016
Lots of Request / Response!
Client Apps
149 characters sent
x 100,000,000

19. Copyright Push Technology 2016
“Point-in-time”
Client A
HTTP Backend
Shorts
Sunglasses
Shorts
Client B
HTTP Request to Save
“Sunglasses” to the list.
HTTP Response
confirming data saved.
?
Client B has no idea
anything has happened!
Client A / User A wants to
add “sunglasses” to the
list of items stored in their
application

20. Copyright Push Technology 2016
Realtime
Client A
Realtime Backend
Shorts
Sunglasses
Realtime API to Save
“Sunglasses” to the list.
Client A / User A wants to
add “sunglasses” to the
list of items stored in their
application
Shorts
Sunglasses
Shorts
Sunglasses
Shorts
Sunglasses
Shorts
Sunglasses
Client B Client C Client D
Persistent Connections,
ensure that updates are
pushed to all clients in
real time

21. Copyright Push Technology 2016
How Push Technology overcomes these challenges…
• Publish / Subscribe integration pattern:
– Realtime – data updates are pushed to clients without polling
• Congested networks need data saving techniques:
– Delta streaming – only transmit what you need
• Robustness during adverse conditions:
– Reliable Reconnect – to overcome unreliable network conditions without data loss
21

22. Copyright Push Technology 2016
Even 2 extra Bytes matters
50,000 concurrent connections
10 updates per second
1.8 Billion messages / hr
Saves 3.6 Billion bytes / hour (3.6 GB)
86.4 GB per day
Over 31.5 TB / year
Image From: http://blog.myrefers.com/2014/08/19/big-data-in-recruiting-is-the-future-of-hiring/thats-a-lot-of-data-big-data-in-recruiting/

23. Copyright Push Technology 201623
Data Efficiency è Attention è Business Value

24. Copyright Push Technology 2016
The Push Technology Checklist
24
Internet optimized
No more wasteful polling
Reduced costs
Efficient data delivery
Low latency

25. Copyright Push Technology 2016
Who we are!
• We’re defining the market for must-have realtime data technology
• Our Realtime Messaging software decouples your backend systems
• And it allows you to overcome the challenges of delivering data via the internet
• Founded 2006; recognised expertise in delivering data at scale and speed
• European HQ in London | Americas HQ in San Jose, CA
25
Selected Customers

26. “One day, all apps will work this way”
Reactive, Responsive, Realtime
Subscribe to our blogFollow us on Twitter Check out our whitepapers
rgarrett@pushtechnology.com
@gssor