Heroku provides a polyglot cloud application platform as a service (PaaS) for building, deploying, and running apps. Lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.
Ruby, Node.js, Java, Python, PHP, etc.
Heroku's slug compiler uses a "buildpack" to prepare your code for execution by the Heroku dyno manager. Includes - PHP, GO!, Scala, Clojure, Erlang, Perl And more…
Postgres, Redis, Mongo, CouchDB, Hadoop, TempDB, MySQL, Elasticsearch, Neo4j
Heroku Button is a powerful tool for deploying code from Heroku with the click of a button. Uber, Dropbox, and Twilio are among the 400+ companies that are finding unique and exciting ways to implement one-click deploys with Heroku Button from their sites.
A lightweight, isolated Unix container running a single user-specified command e.g. web process, worker process like queue or cron job. Can be Scaled Horizontally (Dashboard or CLI) OR Scaled Vertically (e.g. 2X dynos get 1024MB RAM, 4x – 8x CPU)
World's most powerful geospatial database (PostGIS). Open source ORDBMS (Object relational Database). Implements SQL:2011 standard. NoSQL support (JSON). Heroku provides world class hosted Postgres & Nanostuffs has special expertise on setting up Postgres on Heroku Cloud with full suite of Administration Tools.
Automatically synchronizes data between Salesforce and Heroku apps. Provides automatic bi-directional data sync and removes many of the challenging aspects of using the Force.com API. Nanostuffs has applied Heroku Connect to make best use of Salesforce.com as a Backend for several of our built Mobile Apps.
Logs are a stream of time-ordered events aggregated from the output streams of all your app’s running processes, system components, and backing services.
|Codebase||One codebase tracked in revision control, many deploys|
|Dependencies||Explicitly declare and isolate dependencies|
|Config||Store config in the environment|
|Backing Services||Treat backing services as attached resources|
|Build, Release, Run||Strictly separate build and run stages|
|Processes||Execute the app as one or more stateless processes|
|Port Binding||Export services via port binding|
|Concurrency||Scale out via the process model|
|Disposability||Maximize robustness with fast startup and graceful shutdown|
|Dev/Prod Parity||Keep development, staging, and production as similar as possible|
|Logs||Treat logs as event streams|
|Admin Processes||Run admin/management tasks as one-off processes|