Life Technologies' Journey to the Cloud (ENT208) | AWS re:Invent 2013

1,378 views

Published on

Life Technologies initially planned to build out its own data center infrastructure, but when a cost analysis revealed that by using Amazon Web Services the company would save $325,000 in hardware alone for a single new initiative, the company decided to use AWS instead. Within 6 months of adopting AWS, Life Technologies launched their Digital Hub platform in production, which now undergirds Life Technologies' entire instrumentation product suite.This immediately began to decrease their time-to-market and enhance their customers' user experience. In this session, we provide an overview of our path to the AWS cloud, with particular focus on the evaluation criteria used to make a cloud vendor decision. We also discuss the lessons learned since going into production.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,378
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
37
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Life Technologies' Journey to the Cloud (ENT208) | AWS re:Invent 2013

  1. 1. Life Technologies' Journey to the Cloud Mark Field, CTO, Life Technologies November 13, 2013 © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
  2. 2. Life Technologies' Safe Harbor Statement This presentation includes forward-looking statements about our anticipated results that involve risks and uncertainties. Some of the information contained in this presentation, including, but not limited to, statements as to industry trends and Life Technologies' plans, objectives, expectations and strategy for its business, contains forward-looking statements that are subject to risks and uncertainties that could cause actual results or events to differ materially from those expressed or implied by such forward-looking statements. Any statements that are not statements of historical fact are forward-looking statements. When used, the words "believe," "plan," "intend," "anticipate," "target," "estimate," "expect" and the like, and/or future tense or conditional constructions ("will," "may," "could," "should," etc.), or similar expressions, identify certain of these forward-looking statements. Important factors which could cause actual results to differ materially from those in the forward-looking statements are detailed in filings made by Life Technologies with the Securities and Exchange Commission. Life Technologies undertakes no obligation to update or revise any such forward-looking statements to reflect subsequent events or circumstances. © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
  3. 3. About Life Technologies We are a global life-sciences company that believes in the power of science to transform lives To support scientists worldwide, we offer high-quality, innovative products and services – from everyday essentials to sophisticated instruments. • • • • • • • $3.8 billion revenue (2012) 10,000 employees 1,500+ scientists 180 countries 50,000+ products 5,000+ patents & licenses 675,000+ citations Shaping discovery. Improving life.
  4. 4. What We Do Accelerating Scientific Discovery Applying Biology Beyond Research Molecular Diagnostics Our products enable and accelerate research in all areas from discovery to biologics to applications, improving the human condition
  5. 5. This Is Why We’re Here Life-Changing Medicine The Pervenio™ Lung RS test indicated that Jamie Gonzalez, a mother of two who underwent surgery to remove a tumor in her lung, had a very high risk of cancer recurrence. She started on chemotherapy and is now cancer free. Whole-genome sequencing has enabled doctors to provide the Beery twins with a simple, highly effective treatment for a rare condition.
  6. 6. Two Disruptive Technologies Collide Cloud Computing Cloud Computing is the most disruptive technology in the first decade of the twenty-first century Genetic Sequencing Perhaps the most useful tool ever developed to explore the mysteries of human development and disease
  7. 7. Genetics • The Human Genome Project was a milestone in science • Creating the reference genome is the starting point to unraveling the mystery of biology • We have the tools and know how to read, write and understand DNA • Over the next decade we are going to see developments in medical science that will forever change the way we live • Living long and healthy is the most important are of all scientific achievements
  8. 8. “In the Next 10 Years, Data Science Will Do More for Medicine than All Biological Sciences Combined” Vinod Khosla Venture capitalist and founding Chief Executive Officer of Sun Microsystem September 2013
  9. 9. Steps to Obtaining Biological Insight We Can Use 1. Transform biological data into digital data 2. Analyze digitized biological data to gain knowledge 3. Use the knowledge to take informed actions We can do that! But it’s not that simple…
  10. 10. Transform Biological Data into Digital Data • Thousands of scientists around the world are working hard to understand the functions of DNA and RNA • The digitization of biology is critical to understanding the mystery of how life functions • Sophisticated Instruments from Life Technologies and others do this transformation – – • Ion Proton : Full Human Genome Sequencing QuantStudio 3D: digital PCR Where do we store all this data? – – Locally on customer storage Increasingly data is being stored in the cloud
  11. 11. Biological Data Challenge Digitizing biology produces huge volumes of data • 3.2 billion base pairs in the human genome. CGATTTAGGCCT… • One person’s genome from one cell written on a ticker-tape would stretch from NY to LA – Requires massive compute resources to sequence and analyze – Life Tech instruments create an estimated 10 petabytes of data in 2013 – Most researchers and scientists don’t have easy and affordable access to the IT services that the biological data demands
  12. 12. Analyze Digitized Biological Data to Gain Knowledge • • Complex algorithms and software are the essential tools to understanding biological data The computing resources to do this are often huge – Genetic sequencing alignment requires massive compute resource few could afford • • • • Use reference data banks to recognize the biology and know what it does As the biology and scientific knowledge improves, you need to maintain the most up-to-date knowledge bases and provide low-cost global distribution of knowledge Aid the collaboration and participation of all the world’s researchers The most efficient way to provide the compute, data and collaboration is via cloud
  13. 13. Using Biological Knowledge to Take Informed Actions • Application of biological knowledge is very diverse – – – – Cancer is a clear case Rare genetic disease via inheritance Human identification: CSI-type applications helping law enforcement Synthetic biology: Huge potential in biofuel, food production • All require unique applications • Innovative bio apps are being built on the cloud and will have profound impact on all we do – 23andMe.com (great value at just $99)
  14. 14. The Cloud Powers Life Tech’s Digital Hub Vast array of innovative applications Collaborative space to work securely Marketplace to buy products and service Instrument integration Data integration Powered by a powerful cloud infrastructure Storage | Compute | Network External Data
  15. 15. Genomics and Cloud Computing Tackle Cancer
  16. 16. We Are Living Longer AVERAGE LIFE EXPECTANCY AT BIRTH FOR MALES AND FEMALES, 1900–2010 IN THE UNITED STATES Source: U.S. Bureau of the Census 2010
  17. 17. Cancer Will Be the Leading Cause of Death
  18. 18. Cause of Death by Age Group
  19. 19. Cancer Facts • Half of all men and one-third of all women will develop cancer in their lifetime • Cancer is a disease of cells • Cancer begins when DNA is damaged in your cells causing those cells to grow out of control
  20. 20. Cancer and Genetics • Advances in genetics and molecular biology have improved our knowledge of the inner workings of cells • Knowledge and understanding of genetics is helping researchers develop better ways understand, detect and possibly even cure cancer • Sequencing cancer DNA and then analyzing the sequence is how we get the insights into cancer • Sequencing cancer converts the chemical code of DNA into a digital code that computers can store and analyze • Knowledge databases store the known genetic markers of cancer
  21. 21. The Cloud Powers Life Tech’s Digital Hub Vast array of innovative applications Collaborative space to work securely Marketplace to buy products and service Instrument integration Data integration Powered by a powerful cloud infrastructure Storage | Compute | Network External Data
  22. 22. Nice Vision, But How Do You Do That? • Cloud Infrastructure: Build or buy • Bioinformatics platform: Build it because you can’t buy it • Applications : Build, buy, and partner
  23. 23. Life Selects AWS as Infrastructure Cloud Partner
  24. 24. Cloud Provider Landscape (2011) Infrastructure-as-a-Service Market Share Leader AWS Leader in 2011 Gartner IaaS Magic Quadrant (*) Gartner Magic Quadrant for Public Cloud Infrastructure as a Service, 2011 (**) The Wall Street Journal, Meet the Rainmakers, 2011 In 2013 AWS leadership is even greater!
  25. 25. Global Infrastructure for AWS GovCloud (US ITAR Region) North America Ashburn, VA (2) Dallas, TX (2) Hayward, CA Jacksonville, FL Los Angeles, CA (2) Miami, FL Newark, NJ New York, NY (2) Palo Alto, CA Seattle, WA San Jose, CA South Bend, IN St. Louis, MO US West US West (Northern California) (Oregon) US East (Northern Virginia) South America (Sao Paulo) Europe Amsterdam (2) Dublin Frankfurt (2) London (2) Madrid Milan Paris (2) Stockholm EU (Ireland) Asia Australia /NZ Pacific Asia Pacific (Singapore) (Tokyo) (Sydney) Asia Hong Kong Osaka Singapore (2) Tokyo (2) South America Sao Paulo AWS Regions AWS Edge Locations Australia/New Zealand Sydney
  26. 26. Built for Enterprise Security Standards Certifications Physical Security HW, SW, Network SOC 1 Type 2 (formerly SAS-70) Data centers in nondescript facilities Systematic change management ISO 27001 Physical access strictly controlled Phased updates deployment Must pass two-factor authentication at least twice for floor access Safe storage decommission PCI DSS for EC2, S3, EBS, VPC, RDS, ELB, IAM FISMA moderate compliant controls HIPAA & ITAR compliant architecture Physical access logged and audited Automated monitoring and self-audit Advanced network protection
  27. 27. AWS Services We Use Today at Life Technologies
  28. 28. Amazon Web Services (AWS) Life Tech Cloud Platform Components Cloud Applications Panda Aero Pascal Digital Hub Application Platform User Manager App Manager Data Manager Subscription Manager Metrics Manager Instrument Integration Mobile APIs Analytics eBusiness Core IT Systems Flash Comergent, LT.com Portal OAM Identity Management Instrument/Servi ces Portal Corporate IT System E1 (ERP) EDW Middleware Product Search Siebel Agile
  29. 29. Life Tech’s Cloud is LIVE! • Several instruments are now cloud enabled, many more to be released in 2014 • Several SaaS apps are live too, many more in the works for 2014 • Thousands of very happy customers actively using Life Tech cloud service • Much more work ahead…
  30. 30. Impact: Applying Cloud to Scientific Research • Before Cloud – – – – Scientists need to install software on PCs PCs are limited in compute and storage Plate studies restricted to 10 plates per study due to PC memory / CPU size To do more than 10 plates, the scientist needs to collect and analyze data in Excel; very time consuming manual work that is error prone • Moved analysis to the cloud – – – – In the cloud we use large compute instances Can process 150 plates in seconds vs hours Saving scientists days of managing the study in Excel Cost of cloud compute: $4 Full automation and saving days of science time
  31. 31. Cloud Speeds Research by Providing Inexpensive Compute and Storage 120x improvement in plate-processing time
  32. 32. Lessons on How to Succeed at Building a Cloud • Use cloud to transform the relationship with the customer • Give the customer incredible VALUE • Pay attention to developing technical cloud skills • Make reliability your top priority (even before usability) • Security is the top customer concern, so address that first • Use open standards and provide clear architectural governance so that app developers are producing high-quality productively and predictably • Usage metrics are the key to success • Don’t waste time trying to convert everyone, just get support from your top executive • Move fast to beat the innovation killers
  33. 33. Imagine the Possibilities I believe we are entering a new era in science where every researcher has access to technology that reads DNA and super computers to analyze DNA. This will improve our lives in ways we can’t imagine today. Over the next decade we will all benefit from the exciting future made possible by the convergence of cloud computing and genetics.
  34. 34. Life Technologies’ Journey to the Cloud - Recommendations Sean Baumann, Director of Enterprise Software Engineering November 13, 2013 © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
  35. 35. Lifetech AWS Footprint • • • • 4 AWS regions 35+ application environments 11 deployed applications, customer facing 350 average and 1,145 peak EC2 instances
  36. 36. AWS Spend Breakdown AWS Usage EC2 Breakdown EC2 RDS Compute DynamoDB EBS Support Everything Else Everything Else
  37. 37. Architecture
  38. 38. Architecture, AWS Services • Amazon EC2 is the foundation – – • Accelerate application development through use of AWS services – – – – – – – • Substitution for server virtualization Networking features: Amazon Virtual Private Cloud, Elastic Load Balancing, Elastic IP, Amazon Route 53 Save time in database management: Amazon Relational Database Service, Amazon DynamoDB In-memory caching with ElastiCache Decoupling components through queuing: Amazon Simple Queue Service, Amazon Simple Notification Service Flexible storage using web object store: Amazon Simple Storage Service Anticipate dynamic services Architect for failures, reduce dependencies Instances are temporal, services will change Reliability is the priority – – – Multitier architectures, eliminate single points of failure Load balancing, multiple Availability Zones Use tools such as Netflix Simian Army to test resiliency
  39. 39. Lifetech Journey • Identify the business need, focus on innovation • Select a project for demonstrating capability, specific success criteria • Enlist support from organization leadership • Build and organize the cloud team • Execute in an iterative approach • Show value through metrics • Commit to continuous improvement
  40. 40. Gain Leadership Support • Well-defined scope and success criteria for initial project – – – – Start small, show quick wins Consider a proof of concept with short duration Use AWS to fail fast Is success of your cloud project based on functioning software or ability to shorten development cycle? • Educate stakeholders on cloud fundamentals – – – – Difference between public and private cloud TCO calculations, http://aws.amazon.com/tco-calculator/ Low initial investment, quick-start initiatives AWS shared responsibility model • Publish a usage policy – – – Define and enforce acceptable use Clearly state roles and responsibilities across teams Create “contact” with AWS users regarding billing
  41. 41. AWS vs. On Premises Application Services Support Environment Storage Compute On Premises AWS
  42. 42. AWS Usage Pattern EC2 Usage Maximum
  43. 43. Gain Support, Cost Transparency • Show exactly what services are used – Sign up for AWS detailed billing – Consider Netflix ICE https://github.com/Netflix/ice • Tie value to consumed services – Use resource tagging to identify applications and tiers • Show resource utilization – Retire unused resources – Use metrics to determine appropriate resource sizing • Consider alternate architectures – Reduce redundancy for lower environments
  44. 44. Build the Team, DevOps • • Recognize interdependence of software engineering and IT operations Abandon traditional IT silos – • Development Separate teams cause process bottlenecks Define DevOps for your organization – – Blur the lines between development, system administration and QA DevOps is not a separate organization DevOps Quality Assurance Infrastructure Operations
  45. 45. Build the Team, Training • Commit to AWS training – Train the team, not an individual – Utilize AWS reference architectures – Keep up to date on AWS releases
  46. 46. Use Knowledge Resources • Consider AWS support – Several support levels available – Not just for technical issues, but also use case review • Leverage the AWS forums – Collective experience of the developer masses – Get near instant answers to questions • Meet-ups – Learn from people in your local community
  47. 47. Build the Team, Agile • Recruit the right talent, both internal and external – Development team, SCRUM master, product owner • • • • Empower cross-functional development teams to deliver Time-box development through Agile methodology Clearly communicated definition of “done” Principle 10: Simplicity – the art of maximizing the amount of work not done – is essential
  48. 48. Continuous Delivery Less Control DEV More Control TEST Continuous Delivery STAGE Continuous Delivery PROD Continuous Delivery • Restrict control in high-value environments • Lessen developer need to access higher environments • Use automation to create continuous delivery – Remove human error – Ensure code quality
  49. 49. Report on Metrics • Select meaningful metrics, report regularly – – – – – Quality, defects Turn-around, velocity Predictability Resource utilization Cost • Comparison to previous efforts – Select metrics that are equivalent
  50. 50. Continuous Improvement • Assess work completed, set standards – Evaluate technical decisions – If it worked, consider it a standard and publish findings • Be prepared to throw something away – Use “spikes” to try technologies, learn through doing – A solution created during a sprint meets a current need, maybe not the long-term need – Code may need to be refactored as the team learns • Don’t limit improvements to technology – Consider improvements to organization and process – SCRUM retrospectives – Be open with feedback, ask for outside perspectives
  51. 51. Please give us your feedback on this presentation ENT208 As a thank you, we will select prize winners daily for completed surveys!

×