1. 1 Deployment Frameworks for Web Applications John Paul Ashenfelter CTO/Transitionpoint

2. 2 What is a Framework? … a defined support structure in which another software project can be organized and developed. A framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project. From http://en.wikipedia.org/wiki/Framework

3. 3 But Deployment Frameworks?  What does a deployment support structure look like?  What support programs are helpful?  Isn’t each application different?  And shouldn’t my app deploy to any (supported) platform?

4. 4 Do These Questions Sound Familiar?  I have yet to find any examples of websites that have heavy traffic and stream media that run from a ColdFusion platform, can you suggest any sites that will demonstrate that the platform is stable and reliable enough to use on a commercial level?  We are concerned about the long-term viability of ColdFusion as a development language/environment.  How easily can a ColdFusion site be converted to another language? (If for any reason we were forced to abandon ColdFusion at some point in the future or I can’t find someone to work with our code?).  My company has some concerns on whether or not ColdFusion is the right platform to deploy on if we have a very large scale app.

5. 5 What are the Real Questions?  How does the deployment environment scale?  How hard will it be to do in practice  Which components are limiting?

6. 6 What ARE the Parts of Your App?  Network Infrastructure  Server Hardware  Server Software  Application Software  Support Software

7. 7 Deployment Stack: Network  Hardware Speed, in and out Load balancers Firewall Acceleration  Software Compression Monitoring  Services PXE/etc CM LDAP DNS WINS/AD

8. 8 Deployment Stack: Server Hardware  CPU X processors X cores  Memory Bus Timing Channels  Provisioning  Storage Controllers (RAID) NAS SAN  Physical Power Security Cooling  Monitoring

9. 9 Deployment Stack: Server Software  OS version filesystem configuration  Provisioning  Monitoring

10. 10 Deployment Stack: Application Software  Web Server  Application server  Database server  Mail server  Storage server  Security server (LDAP, etc)

11. 11 Deployment Stack: Support Software  Provisioning  Monitoring  Automation  Monitoring  Notification  Monitoring

12. 12 Path to Easier Deployments  KISS  Virtualization is crucial  Automation is essential  Redundancy is key  Measure before you guess  Commit once you measure  Monitor at all times

13. 13 Back-of-the-envelope Calculations  Physical space  Power consumption  Throughput limitations

14. 14 Virtualization  Quick Virtualization Ghost/PXE VPS  True Virtualization Solaris Containers Xen and VPS VMWare

15. 15 Basic Deployment: Pros/Cons  Dell Tower Server  Windows 2003, Standard  IIS  ColdFusion Professional  MS-SQL 2005 Workgroup

16. 16 Common Deployment: Pros/Cons  2x 1u Dell Servers Windows 2003, Web Edition IIS and ColdFusion Professional  1x 2u Dell Server Windows 2003, Standard Edition MS-SQL 2005 Standard Edition

17. 17 Sky’s The Limit Deployment: Pros/Cons  Scaling vertically  Scaling horizontally  Scaling as a service Amazon EC2 and S3 Joyent Containers

18. 18 Questions/Thanks!!!  John Paul Ashenfelter ashenfelterj@transitionpoint.com http://www.transitionpoint.com  Transitionpoint Consulting Training Mentoring