Key Take Away from the webinar

Prerequisites

Heroku Toolbelt

Why are we here ?

• What we are Building • Architectural Overview• Technology Stack Details• Org and Heroku Connect Setup• Live Demo• Q & A

Why ?

• Easy to Start & Configure• Time Saver• Uses Standard Tools• Goodbye to Server Load Balancing• Cheapest for Low Traffic

Case Story

Heroku at Force.com

• Salesforce.com to Heroku Bi-Directional Data Transfer

Force.com + Heroku let you do more

Architecture

• Heroku and Postgres for production web apps

• Salesforce for CRM

• Heroku Connect for to keep Web app data and CRM data in sync

Heroku Connect

• Synchronization as a Service

• Real-time, bi-directional data sync

• Force.com ← → Heroku Postgres

• Point and click Configuration

• Multi-org Support

Heroku Connect

Implementing synchronization with Heroku

Heroku Terminology

Dyno Architecture

Heroku BasicsTerminology

- Procfiles – named commands that you may want executed. Application – consist of your source code, a description of any dependencies, and a Procfile.

- Slug – is an application bundle of your source, fetched dependencies, the language runtime, and compiled/ generated output of the build system – ready for execution.

- Buildpacks – lie behind the slug compilation process. Buildpacks take your application , its dependencies and the language runtime, and produce slugs.

- Dynos – are isolated , virtualized unix containers that provide the environment required to run an application

Heroku + Salesforce Hybrid App

Q & A ?For further queries you can contact Srinivas at

<srinivas.c@saxonglobal.com>

For free Salesforce consultation contact us at info@saxonglobal.com