Download as PDF, PPTX
![Dev[Sec]Ops
DevOps is the combination of cultural philosophies, practices, and tools that
increases an organization’s ability to deliver applications and services at high
velocity: evolving and improving products at a faster pace than organizations
using traditional software development and infrastructure management processes.
This speed enables organizations to better serve their customers and
compete more effectively in the market.](https://image.slidesharecdn.com/20170215effizienteitorganisationenmitdevops-170221171724/75/Aufbau-von-agilen-und-effizienten-IT-Organisationen-mit-DevOps-34-2048.jpg)
Uploaded byAWS Germany
Aufbau von agilen und effizienten IT Organisationen mit DevOps
The document discusses the importance of innovation in modern IT organizations and the need for a shift towards agile and efficient practices, particularly through DevOps. It emphasizes that companies must foster a culture that supports creativity and rapid development to remain competitive while addressing security, compliance, and resource challenges. Additionally, it outlines the transformation at Amazon, highlighting the use of microservices and continuous delivery to improve innovation and operational efficiency.
More Related Content
Similar to Aufbau von agilen und effizienten IT Organisationen mit DevOps
![Agility and Control from AWS [FutureStack16]](https://cdn.slidesharecdn.com/ss_thumbnails/agilityandcontroldougleeaws-161201210211-thumbnail.jpg?width=640&height=640&fit=bounds)
Aufbau von agilen und effizienten IT Organisationen mit DevOps
- 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Steffen Grunwald, Solutions Architect, AWS 21. Februar 2017 Aufbau von agilen und effizienten IT Organisationen mit DevOps
- 2. “Innovation is now recognized as the single most important ingredient in any modern economy. In short, it is innovation – more than the application of capital and labor – that makes the world go round.” Source: http://www.economist.com/node/1324709
- 3. 2/3 More than two-thirds of IT budgets go toward keeping the lights on 77% of CEOs believe security risk has increased in the last few years and 65% believe their risk management capability is falling behind 15yrs The average lifespan of an S&P company dropped from 67 years in the 1920s to 15 years today
- 4. How This Affects You You’re left without the necessary resources to pursue critical business initiatives required to maintain a competitive advantage Your traditional IT model lacks the agility you need to keep pace with innovative startups Insufficient security, compliance and availability can hamper your ability to compete and open the door to sophisticated, hard-to- identify attacks
- 5. Responding requires a new model Focus on differentiating your company Innovate at start-up like speed Reduce risk
- 6. “Instead of being afraid of the challenge and failure, be afraid of avoiding the challenge and doing nothing” Soichiro Honda, Founder of Honda
- 7. 2009 48 280 722 82 2011 2013 2015 AWS Pace of Innovation – new Features and Services 1017 2016 Learn more: https://aws.amazon.com/new/
- 8. “In the past voice interfaces were seen as gimmicks, or a nuisance for driving “hands-free.” The Amazon Echo and Alexa have completely changed that perception. Voice is now seen as potentially the most important interface to interact with the digitally connected world.” Werner Vogels CTO & VP, Amazon.com
- 9. But innovation is hard… …how can companies build an effective innovation system and an environment that will foster and support human creativity and drive technological progress?
- 10. What the heck!? Idon’t recognize this purchase. I want to pay my utility bill I’m about to travel. Please don’t decline my card! I want to transfer money to savings I need to pay my credit card bill How do I order a Venture Card? Scott Totman, Capital One Head of Mobile Technology, Payments & Innovation “Capital One has a state of the art technology platform that allows us to quickly leverage emerging technologies, like Alexa.”
- 11. f(innovation) = (culture * structure) tooling Innovation is the product of culture and structure with the power of tooling.
- 12. f(innovation) = (culture * structure) tooling
- 13. Innovation requires culturethat fosters invention. Culture is the principal component in velocity of innovation.
- 14.
- 15. A company of builders… builders come to build.
- 16. “We've had three big ideas at Amazon that we've stuck with for 18 years, and they're the reason we're successful: Jeff Bezos CEO, Amazon.com Put the customer first. Invent. And be patient.” Jeff Bezos, Amazon CEO
- 17. Focus on the customer and the long term, perspective affects everything.
- 18. We will continue to measure our programs and the effectiveness of our investments analytically…
- 19. We will make bold rather than timid investment decisions …and we will have learned another valuable lesson in either case. …
- 20. “Invention requires two things: the ability to try a lot of experiments, and not having to live with the collateral damage of failed experiments” Andy Jassy, CEO, Amazon Web Services
- 21. Share and give back to innovation.
- 22. This is My Architecture Video Series
- 24. Make time for learning.
- 25. f(innovation) = (culture* structure) tooling
- 26. Good intentions are never enough, you must build structure and create innovation fostering habits.
- 27. The Amazon decision making process is data driven and relies heavily on narratives.
- 28. We always work backwards from the customer.
- 29. Each new idea starts with a write-up of a press release / FAQ. This helps capture the customer perspective of the problem we are trying to solve.
- 30. But how do we remove the bottlenecks?
- 31. A world of conflicting priorities Developers Paid to change things Security Paid to prevent risk Operations Paid to ensure stability
- 32. …and of bottlenecks DevelopmentTesting Security Operations
- 33. Avoid future firefighting by including others early and by investing time to paying back technical debt.
- 34. Dev[Sec]Ops DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.
- 35. “When a feature or enhancement is ready, we push it out and make it instantly available to all.” – Jeff Bezos Speed of iteration beats quality of iteration Encourage single-threaded focus Enables self-directed teams Fosters ownership & autonomy Move Fast and Be Nimble
- 36. “If the development team is frequently called in the middle of the night, automation is the likely outcome. If operations is frequently called, the usual reaction is to grow the operations team.” James Hamilton, Distinguished Engineer, Amazon Web Services
- 37. Amazon.com used to be a monolith…
- 38. 2001 Development transformation at Amazon: 2001-2009 20092006
- 39. Monolithic vs. SOA vs. Microservices SOA Coarse- grained Microservices Fine-grained Monolithic Single Unit
- 40. Small, but not too small Can be rewritten in 2 weeks Owned by a small two pizza team? Balance small and independent with complex interactions
- 41. Composable, Scalable, Polyglot, but not too much Building Microservices – Sam Newman Different teams/tech Independent lifecycle Independent database Fine grained primitives Scope and Ownership (Quality) Standardise Fungible My Enterprise Social Media Service
- 42. Amazon Retail Platform (2009) Chaos?
- 43. Amazon Retail Platform (2009) Organised Chaos.
- 44. Use broad controls that don’t stifle agility.
- 45. While all teams are autonomous, they are defined and driven by the cultural DNA (Leadership Principals) at every step.
- 46. Challenges of Microservices Complexity in Code Base Complexity in Interactions
- 47. Fallacies of distributed computing • The network is reliable. • Latency is zero. • Bandwidth is infinite. • The network is secure. • Topology doesn't change. • There is one administrator. • Transport cost is zero. • The network is homogeneous. Monitoring Auto Scaling Bulkheads Circuit breaker …
- 48. “What we need is a new approach where continuous partial failure is the normal state of affairs.” Michael Nygard
- 49. A measure of innovation agility How many deployments am I performing? How many are done out of hours? How many suffer emergency roll backs? “Too many to count’”“We have a quarterly release cycle” “We minimize customer impact” “Time is irrelevant” “We frequently catch problems too late and need to rollback from pre-release backups” “We roll forwards not back”
- 50. Strive for continuous deployment. Use metrics and tooling to gain trust.
- 51. Continuous Delivery Benefits Improve developer productivity Find and address bugs quickly Deliver updates fasterAutomate the software release process
- 52. f(innovation) = (culture* structure) tooling
- 53. “We own the customer tool” “We own the eCommerce API” “We own the shimblobelter product” “We own the platform” • Tooling • Deployment • Metrics
- 54. Tooling should be decentralised, encouraging self service.
- 55. It should promote best practices WITHOUT being restrictive.
- 56. It should be technology agnostic.
- 57. #1: It should be the path of least resistance.
- 58. Continuous Delivery From check-in to production CI/CD + Release Automation >90% of Amazon teams Pipelines
- 59. 12 years young Rolling Deployments (zero downtime) Health Checking Versioned Artifacts & Rollbacks
- 60. = 50 million deployments a year Thousands of teams + Microservices architectures + Multiple environments + Continuous delivery?
- 61. Deployment != Epic Feature Release Technical debt repayments (refactoring etc.). Security patching. Dependency upgrades. Security, performance, reliability, availability, cost improvements. Adapting to external changes (little and large) with no notice. Fixing defects – meh. Changing schema – agh.
- 62. Great. How does that help me?
- 63. Deployment, Administration & Monitoring MonitorProvisionDeployTestBuildCode Elastic Beanstalk Serverless Cloud Watch Cloud Formation Code Deploy Code Commit CodePipeline CodeBuild
- 64. AWS CodePipeline automatically triggers on new commits into version control (AWS CodeCommit, GitHub, custom…) AWS CodeBuild follows a buildspec.yml file that defines how your application should be built. Common defaults for most languages & dependency repositories. Flexibility to extend with custom Docker images. Testing can be integrated with third party SaaS offerings, Jenkins, or a custom integration. Manual approvals are optional. Deployment options available with AWS CodeDeploy, AWS CloudFormation, AWS Elastic Beanstalk, or custom integrations.
- 65. f(innovation) = (culture * structure) tooling
- 66.
- 67. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved. Steffen Grunwald, Solutions Architect steffeng@amazon.com, @steffeng Thank You.