Cloud Integration with and Heroku

  • Published on

  • View

  • Download

Embed Size (px)


  • 1. Cloud Integration and HerokuDavid Messinger, Appirio, Community Architect@dmessing

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, 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 intellectual property and other litigation, risks associated with 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 products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This 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., inc. assumes no obligation and does not intend to update these forward-looking statements. 3. David MessingerCommunity Architect@dmessing 4. Appirio Helps Enterprises Power Their Business withPublic Cloud Solutions Helping Enterprises Become: EfficientEffectiveAgile Social MobileTechnology-enabled professional services,supported by 500 cloud experts anda 50,000+ cloud developer community5 years, 300 enterprises, 1.5M users moved to the cloud 5. What to Walk Away With Learn strategies on connecting various cloud platforms with Heroku and Learn advantages of different platforms Review examples of using to integrate with cloud platforms. 6. Agenda Brief Intro to Cloud Databases Why we chose Heroku / Example Decomposition of Work Demo Redis Heroku (Ruby/Rails) Q/A 7. NoSQL, NewSQL, YourSQL? What SQL should I use? 8. Database Map by the 451 Group - 2011 9. NoSQL Pros Cons Large data volumes No Joins/Not Relational Flexible Schemas No complex transactions Easy to administer May not guarantee ACID Scales out not up No SQL Specialized DB for the task 10. Document Based 11. Key Valued 12. Graph Based 13. New SQL 14. New SQL Pros/Cons Pros Cons Horizontal scale w/ no Relatively young coding changes Most are not hosted Cost Reduction Server Resources Admin Increased Reliability 15. So What does it All Mean? 16. Historically 17. New Times = New Services Cloud Applications need to be fast. APIs need to be flexible, fast and scalable. RDBMS (in most cases) do not scale for certain types ofapplications. 18. Decoupled Services / Apps 19. Ultimate Ninja DB No ultimate DB No one size fits all Select the right DB Flexible data Big Data Transactional Data 20. Our Selection of 21. CloudSpokesCommuteCalculator ChatterCloud Migration Event Check-in ComplianceHelp DeskMobile App 22. Argh, Chatter Me Mateys 23. Stats 95 Countries 387K Page Views %10 Login Rate 24. CloudSpokes Architecture 25. Why Heroku PaaS vs IaaS Easy to Scale (manual but still easy) No infrastructure resources Heroku vs Cloud Foundry True Public Cloud More mature / Stable not in GA Larger Add on market Git built inCredit: Comparing IAAS and PAAS: A Developers Perspective 26. Heroku Applications Ruby on Rails Java / Play Node.js 27. Heroku Advantages Heroku Addons 28. Why We Settled on database.comA secure, cloud database for building social and mobile enterpriseapps.Slimmed down version of Only custom objects (no CRUD UI) Apex classes, triggers & workflow Identity & user management plus role and profile security OAuth2 & REST baked in Utilize your favorite toolsPricing based upon user licenses, records and transactions 29. adds the fries to the Happy Meal!ApplicationApplication design, development integration and scale Declarative, configuration, reporting 30. Enough Slides! 31. Redis 32. Redis StructureKeyword based search index (Sets) keyword:, (Sets) keyword:To store minimal required data for each challenge (Keys) title:, (Keys) end_date:, (Keys) open:, (Sets) categories:, (Sets) category:To keep track of open and closed challenges (Sets) open_challenges, (Sets) closed_challengesTo keep track of categories (Sets) category_names 33. How To Do Efficient Searches R.sunion(redis_keys)R.sinter(redis_keys) # exclusive key1 = {a,b,c,d}intersect key2 = {c} key1 = {a,b,c,d} key3 = {a,c,e} key2 = {c} sunion {a,b,c,d,e} key3 = {a,c,e} sinter {c} 34. Effective Matching -Metaphone # modified from - vn/lib/text/metaphone.rb def metaphones_for_keywor d(keyword) 35. Demo & Resources Github - Redis Mongo ( 36. David MessingerCommunity Architect @dmessing