This document discusses common pitfalls when building cloud applications on Heroku and provides solutions. It recommends caching everywhere possible to reduce API latency. It also suggests using data replication or synchronization instead of caching to avoid conflicts from bi-directional updates. The document advises warming the API cache with a worker to store static records locally. It also stresses the importance of matching environments between local development and production. Custom APEX endpoints are proposed to reduce API calls and access hidden business logic. Finally, the document emphasizes monitoring logs, load testing applications, and being creative when solving problems.

1. Heroku – Pitfalls and Solutions
Taking the very best of Heroku without surprise !!
Vincent Spehner, Tquila, Heroku Practice Manager
@vzmind

2. Safe harbor
Safe harbor statement under the Private Securities Litigation Reform Act of 1995:
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties
materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results
expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be
deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other
financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new
functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our
operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any
litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our
relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our
service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to
larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is
included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent
fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor
Information section of our Web site.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently
available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions
based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these
forward-looking statements.

3. Introduction
Last year at Dreamforce to interview speakers talking about
Heroku and meet other early adopters of the Platform.
 Released the first version of Heroku Salesforce Playbook on Xmas
2012
• Heroku history
• Introduction to Heroku Toolbelt
• Java and Ruby tutorial to get started
 Next release available soon (Xmas 2013)
• Presenting 15 detailed use cases
• Introduction to the different Salesforce APIs

4. Introduction
Today the objective is to present some common mistakes done
when building Cloud app (including on Heroku) and learn how to
avoid them
 Platform / language neutral
 First we need to understand how Cloud Apps are different ?
• Heroku 12 factors
• Cloud App with remote Data/API

5. Cloud App Architecture

6. The API latency syndrome
How to detect it ?
 Pages taking ages to display
 API Quota reached quickly
 More than 5 API calls per action
SOLUTION : CACHE EVERYWHERE IT’S REQUIRED !!

7. Cache OR Call pattern
Reduce overall API Latency:

8. Understanding Caching options
Cache vs Data replication vs Data synchronization:
 Caching weakness is that you need to sweep it regularly and automate it
 Data replication weakness is that bi-directional update replication implies
potential conflict which need a proper management
 Data synchronization using third party tools such as CloudConnect is a really
convenient way to avoid

9. API cache warming
Principle
 You already know that your application need to get the list of remote
static objects
 Add a worker dedicated to Cache warming
 Store all remote Static records locally
 Define refreshing strategy on the worker itself

10. API cache warming

11. Environment management
Is your local machine the Test env ?
 Heroku app might behave differently than on your Local Machine or
Test Server
• Assets compilation failing
• Process running differently
• Static Configuration
• Memory management

12. Environment management
Solutions:
 Dev ENV as clause of Heroku PROD ENV than possible
 Duplicate your Production ENV for TEST
 Use Foreman locally
 Share Heroku config with your team and load it as part of your ENV
 Of course you can spin up and down TEST env

13. Salesforce custom APEX End Point
Objective:
 Reduce API calls
 Access Hidden Business Logic
Creating custom APEX endpoint:
 Group API calls
 Aggregate multiple records in ONE call
 Trigger complex Apex code from a REST endpoint

14. No clues on errors
Logplex principle
 Logs are an event Stream (12 Factor number XI)
Monitor early, drive safely:
 Start recording logs from the beginning with enough storage capacity
 Monitor your app
 Make sure your logs are relevant

15. Log stream , Papertrail, New Relic

16. App capacity estimation
Load test your app

17. Conclusion
 Be creative
 PoC are not expensive
 Use the right technology/language for the right challenge
 Check the playbook, share your ideas with Book authors

18. All about Tquila
Click to add brief company overview here. Lorem ipsum
dolor sit amet, consectetur adipiscing elit. Sed lectus tortor,
pulvinar sit amet blandit ac, bibendum vitae sapien.
 Click to add implementation highlights; no more than four
 Click to add implementation highlights; no more than four. Lorem
ipsum dolor sit amet, consectetur adipiscing elit.
 Click to add implementation highlights; no more than four
 Click to add implementation highlights; no more than four

19. Vincent Spehner
Heroku Practice Manager,
@vzmind
“If there's anything more important than my ego around, I want it
caught and shot now.” Douglas Adams
“So long, and thanks for all the fish.”
"So once you do know what the question actually is, you'll know what
the answer means.”
“How many roads must a man walk down?”
“Looking up into the night sky is looking into infinity — distance is
incomprehensible and therefore meaningless”

21. Slide parts

22. Slide parts

23. Slide parts

24. Slide parts