Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Geocloud Blue Raster Web Mapping Cloud Deployment - Lessons from the Field 2010-09-21

2,177 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Geocloud Blue Raster Web Mapping Cloud Deployment - Lessons from the Field 2010-09-21

  1. 1. Web Mapping Cloud Deployment- Lessons from the Field<br />Presented by:<br />Michael Lippmann<br />Blue Raster<br />Applications Moving to the Cloud<br />Location Intelligence GeoCloud 2010<br />September 22, 2010<br />
  2. 2. Challenge- Develop/Deploy in 30 days<br />Client<br />Health and Human Services - HRSA<br />Need<br />Health Care Reform 2010 <br />Presidential initiative<br />Double the number of Community Health Centers nationally from 1200 to 2400<br />90 day window to submit grants for a pool of >$1B<br />
  3. 3. Web Mapping Requirement<br />Deploy a web mapping application to assist with grant process <br />Non-negotiable - System must be online when grant period opens<br />Week 1- significant utilization<br />Middle Weeks- use, but not at peak<br />Approaching deadline- last minute use spike<br />
  4. 4. Requirements<br />High availability application<br />Downtime not an option-Redundancy<br />High Performance<br />Subsecond performance for maps<br />Capacity<br />Grant applicants will depend on system<br />$1B+ being applied for<br />
  5. 5. Why we went “Cloud”- Perishable App<br /><ul><li>Ability to scale to immediately- Day 1
  6. 6. Ability to deploy 5 load balanced map servers for peak demand
  7. 7. Managed services for scaling based on use
  8. 8. Lower demand = turn servers off
  9. 9. ESRI Cloud allowed peak use for short period of time
  10. 10. On Day 90- system may be turned off.</li></li></ul><li>Old Way, Cloud Way<br />Old<br /><ul><li>5x Servers
  11. 11. order, setup, deploy, maintain
  12. 12. 5x Licenses
  13. 13. $300k capital
  14. 14. After 90 days not needed!</li></ul>Cloudy – Web Mapping<br /><ul><li>10x Servers
  15. 15. Deploy – right click, wait 5 minutes
  16. 16. 168 Hours x $6/hr = ~$1000
  17. 17. Peak -$1000/week
  18. 18. Non-peak – $250/week
  19. 19. $30k for grant period
  20. 20. Bottom line- allows for scale up/down with much lower capital outlay</li></li></ul><li>How we did it- Hybrid Solution<br />ESRI <br />ArcGISServer -Cloud Infrastructure<br />Amazon<br />EC2<br />ESRI ArcGIS Server for web mapping<br />S3/CloudFront <br />Map tile cache hosting<br />Hosting.com<br />vCloud hosting (using VMware)<br />Adobe ColdFusion<br />Microsoft SQL Server<br />
  21. 21.
  22. 22. Load Estimation<br />
  23. 23. Registrations<br />
  24. 24. UDSmapper.org<br />
  25. 25.
  26. 26. What we Learned-Moving tiles into the cloud-<br /><ul><li>Trying to upload 45 Million map tiles = #FAIL
  27. 27. Simply copying that many files takes >1 day
  28. 28. Load with Amazon Import/Export</li></ul>Use fastest HD you can find- WD 10k SATA<br />Took 20 hours to load files<br />Within 48 hours files are online and ready to use<br /><ul><li>Manage with CloudBerry</li></ul>Change permissions/setup CloudFront<br />
  29. 29. Hybrid Choices<br />Hosting.com Managed Services- Windows 2008 R2<br />Servers online is not as immediate as Amazon- but you have a person to call<br />Machines setup and has 24/7/365 team to monitor and assist as needed<br />Both flavors of Cloud are important in the future.<br />
  30. 30. Launch Day- Plan for Anything<br /><ul><li>You will have DOWNTIME, need to manage it
  31. 31. Launch Day- 2 events caused unplanned downtime</li></ul>Amazon S3 Outage- extremely rare but it happens<br />Datacenter – Cisco switch failure<br />
  32. 32. Health Check your Site<br />Setup tools to watch all of your servers<br />Recommend Pingdom- found it when Twitter had an outage<br />SAAS Monitoring service<br />Uses global array of servers to test and notify of issues<br />
  33. 33.
  34. 34.
  35. 35. Amazon Health Check http://status.aws.amazon.com/<br />
  36. 36. If we did it again… we might:<br />Use even more Amazon S3/CloudFront to cache repeatable operations<br />Geometry request for boundaries- states/counties/HPSA<br />Gzip/cache speeds load<br />Cache directly in Amazon- avoid transfer<br />CloudFront- now has immediate expiration <br />
  37. 37. Risks of Cloud <br /><ul><li>Amazon is great…but many cannot handle unknown risk of elastic pricing
  38. 38. Need team that can administer
  39. 39. Technical saavy – new paradigm
  40. 40. Changes rapidly – must keep up </li></li></ul><li>Conclusions/Questions<br /><ul><li>Deployment was successful, next one will be easier and better
  41. 41. Cloud for web mapping cannot be ignored
  42. 42. Hybrid solutions work very well
  43. 43. Focus on your business requirements, outsource all of the rest
  44. 44. Simple is always best</li></li></ul><li>For more information:<br />Michael Lippmann<br />mlippmann@blueraster.com<br />703-875-0914<br />www.blueraster.com<br />blog.blueraster.com<br />@blueraster<br />
  45. 45. Diagram on top of UDS Mapper<br />

×