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.
Dynamic Infrastructure
Matthew Flaming, VP Site Engineering
@mflaming
This document and the information herein (including any information that may be incorporated by reference) is provided for...
A Brief History of Ops
A Brief History of Ops
A Brief History of Ops
A Brief History of Ops
COMPLEXITY
(like entropy)
Grows Over Time
• HW issues

• OS upgrades

• Disk space

• CPU usage
• HW issues

• OS upgrades

• Disk space

• CPU usage

• Network iss...
• 3+ year lifespan

• a few hosts

• quarterly releases
• 1+ year lifespan

• tens of hosts

• monthly releases
• 6 month ...
EMBRACE
The Problem
“oh sh*t, scale, complexity, and
volatility are eating us alive!”
“Our architecture needs to be built
for scale and volati...
Dynamic Infrastructure is a Design Pattern
Phoenix Servers Compute as a
Uniform Resource
Know Your Herd
INFRASTRUCTURE
As
CODE
Spec
Build
Test
Deploy
Promote
Monitor
CODE
Defines
INFRASTRUCTURE
Standardized
Shutdown hooks
Standardized
Config
Standardized
Health checks
Horizontally
Scaled
Stateless
or
Replicated
TOMORROW
Is An Inexact Science
Thank you.
Matthew Flaming, VP Site Engineering
@mflaming
APPENDIX
WELCOME TO
FUTURESTACK 16
Upcoming SlideShare
Loading in …5
×

Track Welcome: Operating Dynamic Infrastructure [FutureStack]

105 views

Published on

Track Welcome: Operating Dynamic Infrastructure
Speaker: Matthew Flaming, VP of Engineering, New Relic

Published in: Data & Analytics
  • Be the first to comment

  • Be the first to like this

Track Welcome: Operating Dynamic Infrastructure [FutureStack]

  1. 1. Dynamic Infrastructure Matthew Flaming, VP Site Engineering @mflaming
  2. 2. This document and the information herein (including any information that may be incorporated by reference) is provided for informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc. (“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission. Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the statement will include words such as “believes,” “anticipates,”, “expects” or words of similar import. Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof, and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect such forward-looking statements is included in the filings New Relic makes with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at ir.newrelic.com or the SEC’s website at www.sec.gov. New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New Relic makes no warranties, expressed or implied, in this document or otherwise, with respect to the information provided.
  3. 3. A Brief History of Ops
  4. 4. A Brief History of Ops
  5. 5. A Brief History of Ops
  6. 6. A Brief History of Ops
  7. 7. COMPLEXITY (like entropy) Grows Over Time
  8. 8. • HW issues • OS upgrades • Disk space • CPU usage • HW issues • OS upgrades • Disk space • CPU usage • Network issues • Noisy neighbors • OS upgrades • Disk space • CPU usage • Network issues • SOA complexity • HW issues • Noisy neighbors • OS upgrades • Disk space • CPU usage • Network issues • SOA complexity • Container issues
  9. 9. • 3+ year lifespan • a few hosts • quarterly releases • 1+ year lifespan • tens of hosts • monthly releases • 6 month lifespan • hundreds of VMs • weekly releases • 1 month lifespan • thousands of containers • daily releases
  10. 10. EMBRACE The Problem
  11. 11. “oh sh*t, scale, complexity, and volatility are eating us alive!” “Our architecture needs to be built for scale and volatility, while reducing complexity.” Dynamic Infrastructure dynamic infrastructure
  12. 12. Dynamic Infrastructure is a Design Pattern Phoenix Servers Compute as a Uniform Resource
  13. 13. Know Your Herd
  14. 14. INFRASTRUCTURE As CODE
  15. 15. Spec Build Test Deploy Promote Monitor
  16. 16. CODE Defines INFRASTRUCTURE
  17. 17. Standardized Shutdown hooks Standardized Config Standardized Health checks Horizontally Scaled Stateless or Replicated
  18. 18. TOMORROW Is An Inexact Science
  19. 19. Thank you. Matthew Flaming, VP Site Engineering @mflaming
  20. 20. APPENDIX
  21. 21. WELCOME TO FUTURESTACK 16

×