1. Leapfrogging with Legacy…
or bite the bullet?
ARCHITECTING A BALANCED PRODUCT
PORTFOLIO FOR, SMALL, MEDIUM, LARGE.

2. The Week the Cloud Won
IT players "who thought they had...years to adjust to the new
realities...having a really bad day”
by Quentin Hardy NYT

3. Perspective
 2012 looking like 1992
 Previous era synchronous technologies, Voice, Windows, stick
around, but not suited to asynchronous global business
communications.
 The Browser, having successfully incubated JavaScript as the
canonical era asynchronous development platform, now fading
away.
 User experience, ushers in Apps economy, iPAD, Android,
HTML5.
 Client-side JavaScript now moving to server-side for
asynchronous collaboration at scale, NodeJS, WebSockets,
push notifications.

4. How to pull a Kobayashi
Maru with legacy?
A no-win situation caused by a set of rules that can
only be won by changing the rules, in effect,
cheating...

5. http://youtu.be/z49bBPf7b4g
Solving the Kobayashi Maru…
A Starfleet training exercise designed to test the character of cadets in the
command track ...

6. Lets cheat..
 Training exercise: By way of my work and development
community involvement I’m constantly learning latest
technologies, new approaches and rubbing shoulders
with top practitioners.
 Change the rules: A polyglot PaaS approach
 Test the approach

7. Design
STORIES, VISUALIZATION, USER EXERIENCE

8. Have you ever wondered
where things come from?

10. Product Development
WIINING CUSTOMERS WITH CONVENIENCE OVER SOPHISTICATION,
USER EXPERIENCE OVER FEATURES

11. Software architecture
priorities evolved
Image: Barbara Agnew

12. Development
 Web Dev UX NOT UI Dev
 Beautiful design practices for
communication and viral
adoption
 API easy to adopt
 Sample App – code pushed
to GitHub
 Twitter API
 Exploreable
 Predictable
 Consistent
Alex Payne @al3x
Stanford cs547 HCI
http://youtu.be/VVovVjT_H8A

13. Why polyglot PaaS approach
 Polyglot (multi-technology)
 Polystore (multi-datastore)
 SQL, NoSQL, NewSQL
 PaaS
 NoOps, No Admin, Automated scaling
 AWS / Azure / Heroku (CouchDB)
 CouchDB
 Part of the NoSQL group of data stores and is designed for local
replication and to scale horizontally across a wide range of devices.
 Supported by commercial enterprises Couchbase and Cloudant.
 User Experience: Expedia / Cassandra
 price book (2 billion) wide rows are not always bad
 http://slidesha.re/vxlErt

14. Marketing
MARKETING SHIFTS TO PERSUASION TECHNOLOGIES:
Dave McClure
METRICS FED BACK INTO PRODUCT DEVELOPMENT ITERATIONS:
Eric Ries

15. Internet companies…

16. .
SFDC growth
strategy…
The Social Enterprise, has just
begun.

17. Polyglot PaaS approach…
REMOVE FEATURES, FOCUS ON USER EXPERIENCE
TIER 3 PRODUCT FROM
TIER 1 -2 LEGACY?

18. Product transformation-1
Tier 1 – 2 Tier 3
Enterprise Social / Mobile
Legacy Cloud
Application sign in API = read New
UI ux UX = low latency
SDK == Application=0
On Hypervisor
Premise Hosting
Data Base

19. Product coexistence-2
 SaaS biz apps generally use multitenant database.
 Disruptive to back-fit legacy with MT database.
 Another way of filtering identity to data views?
 Granular data social objects: PaaS approach
 Database.com (live), Pardalis.com (patents)

20. Few features, strong UX -3
Tier 1 – 2 Tier 3
Enterprise Social / Mobile
Legacy Cloud
Application New write API = read
UI UX UX = low latency
SDK minimal Application=1
On Hypervisor
Premise Hosting
Data Base

21. Summary
Tier 1- 2 Tier 3
 Assumes legacy apps  Code API Mobile reads
already supported on
industry standard VM  Select cloud sign-on and
hypervisors. VM hosting vendor
 Assumes customization  App to learn and
by SDK or DB, making neutralize new entrants
legacy product on
premise.  Select granular data filter
polyglot
 Develop API for writes
 Iterate

22. Continue to transformation..?
Following may be phased in as market pressure grows

23. Transformational separtion-4
Enterprise Tier 1-2-3
Legacy Social / Mobile
Template Cloud
Application Information API = read
UI UX = low latency
Analytics
Hosting
SDK Application=2
Database Database
meta
schema+

24. CouchDB: Cloudant.com
 Cloudant's hosted data layer service makes clustering
similar to Voldemort, Cassandra, or Riak, as it
implements a version of Amazon's Dynamo
 Rest API http: post, get, put, delete (CRUD)
 Distributed Architecture with bi-direction sync
replication and off-line replication.

25. Transformational
 Cloudant's hosted data
layer service Tier 1-2-3
Social / Mobile
 Rest API Cloud
 Distributed
Architecture with sync Information API = read
off-line replication.
UX = low latency
Analytics
Hosting
Application=2
Asia US UK Europe

26. Result: service for small, product
for medium, large -5
Tier 1 – 2 Tier 3
Enterprise Social / Mobile
Legacy Cloud
Application Information API = read
UI UX = low latency
UI
Analytics
SDK Application=1 Hosting
On
Premise
Database Asia US UK Europe

27. Conclusion
 Creative Polyglot PaaS approach seeds tier 3.
 Feature deep tier 1 and 2 not disrupted.
 Implementation details are product specific
 Boilerplate with polyglot PaaS based on CouchDB
(other polyglot polystore solutions may fit better)
 Each product development team to follow the
prescribed methods (no bottlenecks expected)

28. Reference
 High level solution by Clive
Boultonhttp://about.me/cliveboulton
 Specialist in enterprise connected consumer product R&D
 Detailed implementation guidance available :)
 Hypervisor Comparison by VMGuru.nl
 Stephen Smith’s blog. CSA Sage Group plc.
 GTUG community / Seattle Hadoop Scalability meetup
 All referenced works attributions to respective authors / owners.