Create a Force.com-Powered Facebook App on Heroku
Download as PPTX, PDF1 like2,185 views
The document outlines a presentation on creating a Facebook app using Heroku and integrating it with the Force.com platform. It highlights the importance of best practices, such as using memcache for efficiency and PostgreSQL for storing votes. Additionally, it provides a safe harbor statement regarding potential risks and uncertainties related to forward-looking statements made during the presentation.
Create a Force.com-Powered Facebook App on Heroku
- 1. Create a Force.com- Powered Facebook App on Heroku Pat Patterson @metadaddy Principal Developer Evangelist salesforce.com
- 2. Safe Harbor Statement “Safe harbor” statement under the Private Securities Litigation Reform Act of 1995: This presentation and the oral remarks that accompany it contain forward-looking statements the achievement of which involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions proves incorrect, our results 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 statements concerning new, planned or upgraded services or technology developments, any projections of subscriber growth, earnings, revenues or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief and statements about future customer contracts or future customer use of our services. The risks and uncertainties referred to above include - but are not limited to - interruptions or delays in our service or our Web hosting; our ability to complete and successfully release new and improved versions of our on-demand platform and development environment; our new business model; problems integrating, launching or operating services based on newly acquired businesses or technologies, breach of our security measures; possible fluctuations in our operating results and rate of growth; the emerging market in which we operate; our relatively limited operating history; our ability to hire, retain and motivate our employees and manage our growth; competition; our ability to continue to release and gain customer acceptance of new and improved versions of our CRM service; unanticipated changes in our effective tax rate; fluctuations in the number of shares outstanding; the price of such shares; foreign currency exchange rates and interest rates. Further information on these and other factors that could affect our financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings we make with the Securities and Exchange Commission from time to time, including our Form 10-K for the fiscal year ended January 31, 2007. These documents are available on the SEC Filings section of the Investor Information section of our website at www.salesforce.com/investor. Any unreleased services or features referenced in this or other 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 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, except as required by law.
- 3. Agenda • Brief overview of Heroku • Create a Facebook app with Heroku – Pull data from Force.com – Show some best practices – Give away some money!
- 4. 1,250,000+ Apps Running on Heroku
- 5. The Heroku Cloud Application Platform Run Anything Forget Servers $ heroku create -s cedar Deploy Instantly $ git push heroku master Scale with Ease Extend with Add-ons
- 6. Heroku and Facebook: Even Simpler!
- 7. The Brief • Create a Facebook app to – Retrieve a list of charities from Force.com – Collect votes on charities – Restrict users to a single vote • Create a Force.com app to – Manage the list of charities – When the contest is over, initiate the approval process for a donation to the winning charity
- 8. Charity App Back-end • Let’s look at how employees manage charities in Force.com
- 9. Force.com REST API • Authenticate/authorize access via OAuth 2.0 • Records in Force.com identified by URLs – /services/data/v24.0/sobjects/Charity__c/a0 0d0000002XU4r • CRUD via POST/GET/PATCH/DELETE • SOQL query interface – /services/data/v24.0/query?q=SELECT+Na me+FROM+Charity__c
- 10. Step 1 • Let’s extend our basic Facebook app to pull charity data from Force.com
- 11. Efficiency • App gets charity data from Force.com on every page view – GOOD: data is timely – BAD: resource consumption, performance
- 12. Best Practice • Let’s use Memcache to store charity data – Facebook app loads cache from Force.com – Force.com trigger flushes cache on any change
- 13. Step 2 • Add Memcacheaddon • Store charity data in Memcache • Configure Force.com app to flush cache on any change to charity data
- 14. Let’s Get Voting! • But where do we store votes?
- 15. HerokuPostgres • Managed SQL database • Free shared-database addon for development • Several tiers of paid service for production
- 16. Step 3 • Store votes in Postgres • Expose vote totals via RESTful Web service • Integrate with approval process in Force.com
- 17. Vote • Insert Heroku app URL here!
- 18. Conclusion • Use Heroku for your high-volume Facebook apps • Use the Force.com REST API to integrate external apps with Force.com • Integration is straightforward, but follow best practices to get a great result!
- 19. Resources www.heroku.com/facebook developer.force.com/REST workbench.developerforce.com bit.ly/cs12-facebook
Editor's Notes
- #2: Pre-session checklist: facebook dev page, workbench, Heroku home page, https://addons.heroku.com/
- #5: Show ‘Trust & Manage’ tab of Heroku website to see current number
- #6: Heroku makes cloud development simple
- #7: Create a default Facebook app in Heroku. git clone to retrieve source. Point out envvars for config, mogli for Facebook Graph API interactions.
- #9: Show ‘Charities’ tab in Cloudstock app in Force.com
- #10: Show workbench to query data
- #11: Copy over ‘stage 1’ source code. Point out oauth2 Ruby gem, new envvars for Force.com credentials, OAuth 2.0 log in, one line of code to pull charities from Force.com, code in index.erb to show charities. Commit, push to heroku, try running – oops!!! No values for envvars! Run script to set env vars. Try running again. Invite audience to hit app. Refresh app a few times. Explain how it’s likely a bit slow, since all traffic is being handled by a single dyno – let’s fix that right now by scaling it to 5 dynos.
- #12: Make a change to one of the charity’s logos then refresh to show that we do always see fresh data. Invite audience to hit app. Go to Force.com System Overview page and show API usage increasing as the page is hit.
- #13: Go to Herokuaddons page to point out Memcache add on.
- #14: AddMemcacheaddon, copy over ‘stage 2’ source code, point out use of Dalli Ruby gem for Memcache. Point out caching – charity data, plus access token/instance URL for Force.com. Point out cache flush code. Go to Force.com app, show trigger, cache flush method, update remote site setting, custom setting. Push new code. Invite audience to start hitting the app and watch the API Usage meter not change. Reverse the change we made earlier in Force.com and show that charity data is updated, and API usage incremented once.
- #15: Our brief says we need to integrate with approvals, so our Force.com app needs access to voting data, but where do we actually store it? Ask the audience – where should we store the votes?
- #16: Go to addons page and show levels of HerokuPostgres service.
- #17: Add shared-databaseaddon. Point out DataMapper usage, voting functionality – jQuery click handler posts vote to Ruby app
- #18: Refresh the page a few times as the votes come in. When audience is all done, show code in FB app to return vote counts. Go to Force.com and show code to pull vote counts, initiate approval. Go to VF page and show vote counts, click button to initiate approval, show record is locked for approval.