Shelly cloud & heroku & engineyard. Pros & Cons

2,765 views
2,487 views

Published on

Introducing different PaaS, pros and cons.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,765
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Shelly cloud & heroku & engineyard. Pros & Cons

  1. 1. Shelly Cloud,Heroku& EngineYardPros & ConsGiedrius Rimkus & Viačeslavas ČičkinasRuby Conference Lithuania2013 April
  2. 2. Thats not a battleIts not about which one is better.. its allabout showing the pros & cons of thoseplatforms..In the end.. its up to you to choose the rightone!
  3. 3. Cloud Computing?Pay-per-use (or pay-as-you-go)On-demandComputing resources
  4. 4. So what are those services?Delivering platform as a serviceDeployments are done by pushing with gitCompetence needed? No! Its simple as that!
  5. 5. What is PaaS?
  6. 6. Example of git push at ShellyCloud$ git push myapp-production masterCounting objects: 74, done.Delta compression using up to 4 threads.Compressing objects: 100% (47/47), done.Writing objects: 100% (47/47), 5.60 KiB, done.Total 47 (delta 39), reused 0 (delta 0)remote:remote: ---> Received push to cloud mymapp-productionremote: ---> Checking Gemfileremote: ---> Deploying your applicationremote:remote: ---> Deployment on server app1 startedremote: ---> Deployment on server app1 finishedremote:remote: ---> Deployment successfulTo git@git.shellycloud.com:myapp-production.git9ce50af..00a4ab4 master -> master
  7. 7. Example of git push at Heroku$ git push heroku master-----> Heroku receiving push-----> Rails app detected-----> Compiled slug size is 8.0MB-----> Launching... done, v1http://sushi.herokuapp.com deployed toHeroku
  8. 8. Example of git push at EngineYardEither through the web dashboard or CLI1. GUI:2. CLI:ey deploy --environment=example_production --app="new_rails_app" --account="Example"
  9. 9. AimHide all administration stuffDevelopers focus on building application andnot on deployment nor infrastructure
  10. 10. Management via command line toolshelly - cli for ShellyCloudheroku-toolbelt - cli for Herokuey (engineyard gem) - cli for EngineYard
  11. 11. Infrastructure managementCloudfile in ShellyCloudWeb based, Procfile - in HerokuWeb based, API (now in beta,coming soon) - inEngineYard
  12. 12. ShellyCloud architecture
  13. 13. Heroku architecture
  14. 14. Engine Yard architecture
  15. 15. PricingHeroku- per process / workerEngineYard- per instanceShelly Cloud- per instance
  16. 16. Supported languagesHeroku supports many platforms: Ruby, Java,Python, Clojure, Scala, Node.jsEngineYard supports: PHP, Ruby, Node.jsShellyCloud is Ruby oriented.
  17. 17. FREE plansApplication with only 1 worker is always FREEat Heroku.Engine Yard has a free trial, that offers 500 freeHoursShellyCloud offers 20 credit for the first cloud,thats 1 month for FREE.
  18. 18. File storageStoring files at Shelly Cloud local storageshared among all app instancesHeroku you need S3 (simple storage service)EngineYard attaches separate EBS Volume toevery instance. Snapshots and Backups areautomatically uploaded to designated S3bucket. You can use your own S3 Bucket aswell.
  19. 19. Sending emailsShellyCloud provides already configured mailserversHeroku external service has to be used, i.e."Sendgrid"EngineYard external service in form of addonshas to be used, i.e. "Sendgrid", "Mailgun"
  20. 20. Databases supportedShellyCloud - PostgreSQL, Redis, MongoDBHeroku - PostgreSQL, MySQL, Redis,MongoDBEngineYard - PostgreSQL, MySQL, Riak,MongoDB, Redis
  21. 21. Questions?
  22. 22. Thank YouGiedrius RimkusSoftware Engineer@giedriusrViačeslavas ČičkinasBusiness Development Representativeat EngineYard@vcickinasRuby Conference Lithuania. 20 April, 2013

×