migrating to rails 3, an in-house developers perspective

Chetan Krishna and Mark Johnson

Migrating To Rails 3 An In-house Developer's

Perspective

Wednesday, May 18, 2011

Who Are We?

• Our Company

• Publicly Traded

• > 150 M/year Rev

• > 600 Employees

• Offices World Wide

• Us

• Development Team

• CIO Rails Advocate

• Develop & Maintain

• 24x7 Support

• Web Apps > 12yrs

• Rails since 2006


Challenges

Approaches


Legacy Environment

Not OONot MVCNo Testing


Adoption Challenges

Maintenance

Integration

Technology

Migration


Our Application Environment

Legacy Non-Rails AppsWeb & Client Server11 Apps

Commercial AppsFinancials and HR& Sabrix (sales tax)

Rails 1 - 7 AppsRails 2 - 56 AppsRails 3 - 5 Apps


Sales Management

Quotes/Orders

Leads Sales

PRESE

Reports

Dashboards

Accounts

Partners

Customer Directory

CalendarAsterisk


Approaches

Creating new apps

Background jobs

Data Sharing

App Configuration

Authentication


68 apps in production


Templates

• create only what we need

• update specific parts of the app


Templates


Approaches

Creating new apps

Background jobs

Data Sharing

App Configuration

Authentication


Background Jobs

flexible schedule

notify on exceptions

daemons


Background jobs


Approaches

Creating new apps

Background jobs

Data Sharing

App Configuration

Authentication


Data Sharing

Data SynchronizationReading and Writing between apps


4D

Core Data Synchronization


4D

Rails

Core Data Synchronization


Topic Subscribers

Publisher

Subscribers

Subscribers

Subscribers

Topic


Topic Subscribers

app/models/company.rb


Topic Subscriberslib/daemons/push_updates_to_sales.rb


Data Sharing

Data SynchronizationReading and Writing between apps


Quotes/Orders

Leads Sales

PRESE

Reports

Dashboards

Accounts

Partners

Customer Directory

CalendarAsterisk

Shared DB for Multiple Apps


Shared DB for Multiple Apps

Sales AppLeads Appleads opportunities

sales_db


Shared DB for Multiple Appsleads/app/models/opportunity.rb

leads/app/models/opportunity_resource.rb


Different DBs for Single App

Quotes/Orders

Leads Sales

PRESE

Reports

Dashboards

Accounts

Partners

Customer Directory

CalendarAsterisk



leads opportunities

sales_db

partners_db

Reporter App



app/models/registration.rb

app/models/opportunity.rb

reporter/config/database.yml


reporter_db

localhost


Reporter App sales_dbsales_db


reporter_db

localhost


sales_dbReporter

Appsales_db(replicated)


Approaches

Creating new apps

Background jobs

Data Sharing

App Configuration

Authentication


Authentication


• Existing

• Domain Cookie

• Encrypted Credentials

• Distributed

Single Sign-on / Sign-off

• New

• Rails as Master

• Support Legacy Apps

• Support 3rd Party Apps


Implemented Oauth2 Provider and Client

http://www.railsatwork.com/2010/10/implementing-oauth-provider-part-1.html

Application AuthenticationProvider

Browser

Access Token

Domain CookieDomain Cookie

Authorization Token




Approaches

Creating new apps

Background jobs

Data Sharing

App Configuration

Authentication


database.yml Setup


Application Specific Configuration Data

app/models/opportunity_resource.rb


Application Specific Configuration Data


E-mail

Oh, $#*&!

Did that e-mail from development just get sent to the client?


ActionMailer Interceptor


ActionMailer Interceptorconfig/environments/development.rb


ActionMailer Interceptor


Questions

Chetan [email protected]

Mark [email protected]

Rails At Workhttp://www.railsatwork.com/


mailto:[email protected]






migrating to rails 3, an in-house developers perspective

Technology

apps rails

background jobswednesday

data synchronizationreading

employees web apps

different dbs

single app localhost

db reporter appsales

shared db