Java Tech & Tools | Deploying Java & Play Framework Apps to the Cloud | Sandeep Bhanot
2 likes1,894 views
This document discusses deploying Java and Play! applications on Heroku. It describes how Heroku provides a managed platform-as-a-service that eliminates the need to provision and manage servers and software stacks. With Heroku, developers can focus on their code without worrying about operations. The document provides examples of using common Heroku commands to deploy an app, connect to databases, create worker processes, and use add-ons. It also gives a brief overview of the Play! web framework and how to deploy Play! apps on Heroku.
![Transform DATABASE_URL
Heroku:
postgres://[username]:[password]@[server]/[db-name]
JDBC:
jdbc:postgresql://[server]/[db-name]?user=[username]&password=[password]
Transform:
dbUrl = dbUrl.replaceAll("postgres://(.*):(.*)@(.*)",
"jdbc:postgresql://$3?user=$1&password=$2");](https://image.slidesharecdn.com/2sandeepbhanotdeployingjavaplayframeworkappstothecloud-111108114220-phpapp02/85/Java-Tech-Tools-Deploying-Java-Play-Framework-Apps-to-the-Cloud-Sandeep-Bhanot-24-320.jpg)
Java Tech & Tools | Deploying Java & Play Framework Apps to the Cloud | Sandeep Bhanot
- 1. Deploying Java and Play! Apps on Heroku Sandeep Bhanot @cloudysan
- 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 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 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-Q for the most recent fiscal quarter ended April 30, 2011. 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. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Proprietary & Confidential
- 3. Once upon a time…. Tim wanted to develop a Java app……
- 4. So he got to work…. • Acquire and provision all the H/W (Servers, Load Balancers, Routers etc.) • Install, configure and tune the entire S/W stack (OS, Web/App Server, DB etc.) • Configure env. for Application services like Routing, Clustering, Load Balancing, DR, Caching, DB Replication etc ($$$) • Patch and upgrade the H/W and S/W stack Cost Agility
- 5. One day…. Tim decided to try this ‘Cloud’ thingy……
- 6. So he tried an IAAS provider…. • NO H/W to buy/install/configure! • Still has to configure and tune the entire S/W stack (OS, Web/App Server, DB etc.) • Still has to configure (and sometime code) env. for Application services like Scaling, Routing, Clustering, Load Balancing, DR, DB replication etc • Patch and upgrade the S/W stack Cost Agility
- 7. Finally…. Tim heard of Heroku
- 8. When Tim met Heroku…. • NO Servers • Managed S/W stack (OS, Web/App Server, DB etc.) • Application services like Routing, Load Balancing and DR built-in • Elastic scaling • git push heroku master Focus on your Code. Period. Cost Agility
- 9. Heroku = Polyglot Cloud Platform 402,550+ Apps Running on Heroku
- 10. $ heroku create –s cedar $ git push heroku master
- 11. Create more web processes: $ heroku scale web=2 What processes are running: $ heroku ps
- 12. Check the logs: $ heroku logs
- 13. View releases: $ heroku releases Rollback: $ heroku rollback
- 14. Run a process: $ heroku run "your bash command"
- 16. Deploying web apps... Environment (Runtime, configuration, etc) Ingredients (Dependencies, app, services, etc) Process (Build, assemble, start, etc) Environment + Ingredients + Process = web 1! Environment + Ingredients + Process = web 2!
- 17. Externalize Environment Variables $ heroku config DATABASE_URL = postgres://blah:blah@ec2.compute-1.amazonaws.com/blah JAVA_OPTS = -Xmx384m -Xss256k -XX:+UseCompressedOops MAVEN_OPTS = -Xmx384m -Xss256k -XX:+UseCompressedOops PATH = .maven/bin:/usr/local/bin:/usr/bin:/bin REDISTOGO_URL = redis://redistogo:1234asdf@angler.redistogo.com:9291/ REPO = /app/.m2/repository
- 18. Ingredients defined (pom.xml) <dependency> <groupId>org.eclipse.jetty</groupId> <artifactId>jetty-webapp</artifactId> <version>${jetty.version}</version> </dependency> <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>jsp-2.1-glassfish</artifactId> <version>2.1.v20100127</version> </dependency> <dependency> <groupId>postgresql</groupId> <artifactId>postgresql</artifactId> <version>9.0-801.jdbc4</version> </dependency>
- 19. Process defined (Maven + Procfile) web: sh target/bin/webapp
- 21. Share-Nothing Move state to the isolated & independent edges - UI state -> client - Permanent state -> external data stores
- 22. Deploy an app on Heroku 1. Create a Java Web App 2. Add a Procfile 3. Commit to a git repo 4. Create an app on Heroku 5. “git push” to Heroku 6. Scale and monitor on Heroku
- 23. Connect to a Database • Free shared PostgreSQL DB • Dedicated & managed PostgreSQL DB • Amazon RDS MySQL & Oracle • NoSQL Add-ons (Redis, MongoDB, etc) • Database.com • Or do your own thing
- 24. Transform DATABASE_URL Heroku: postgres://[username]:[password]@[server]/[db-name] JDBC: jdbc:postgresql://[server]/[db-name]?user=[username]&password=[password] Transform: dbUrl = dbUrl.replaceAll("postgres://(.*):(.*)@(.*)", "jdbc:postgresql://$3?user=$1&password=$2");
- 25. Create a Worker Process 1. Create a process 2. Update the Procfile 3. Push to Heroku 4. Scale the workers
- 26. Using a Heroku Add-on • Find an Add-on: http://addons.heroku.com • Activate the Add-on • Use the service • Push to Heroku
- 27. Play! • A Java framework for Web Applications • Non Servlet or JEE based • A full stack framework • Focuses on productivity and fun
- 28. Play! on Heroku 1. Create Play app 2. Add app to git repo 3. Create app on Heroku 4. Push app to Heroku
- 29. 750 free dyno hours per month per app