Malmberg, an educational publisher, wanted to improve the speed and efficiency of releasing new features. They transitioned to a container-based continuous delivery model where development and operations teams work together through all stages of the product lifecycle. Key principles of their approach include having an automatically releasable master branch, extensive automated testing of all code changes, and treating infrastructure as code. This has led to benefits like increased agility through faster release cycles and availability through auto-scaling and proactive monitoring.
DevOps is not just a practice, designation or concept, it is a smart collaboration between software developers and IT professionals, DevOps has become a most requirement for all big and mid-size organizations.
DevOps is not just a practice, designation or concept, it is a smart collaboration between software developers and IT professionals, DevOps has become a most requirement for all big and mid-size organizations.
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Inverting Test Pyramid - A First Hand Experience ReportNaresh Jain
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Business Impact:
* Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
* Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
* Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report
Conference: http://pune.agileindia.org/
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
In many organizations, agile development processes are driving the pursuit of faster software releases, which has spawned a set of new practices called DevOps. DevOps stresses communications and integration between development and operations, including continuous integration, continuous delivery, and rapid deployments. Because DevOps practices require confidence that changes made to the code base will function as expected. automated testing is an essential ingredient Join Jeff Payne as he discusses the unique challenges associated with integrating automated testing into continuous integration/continuous delivery (CI/CD) environments. Learn the internals of how CI/CD works, appropriate tooling, and test integration points. Find out howpto integrate your existing test automation frameworks into a DevOps environment and leave with roadmap for integrating test automation with continuous integration and delivery.
Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony
Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions:
- Who are the people I need in place?
- What are the core processes that I need to change?
- What tools do I need?
View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar
Behavior driven development - Deliver Value by CollaborationNaveen Kumar Singh
BDD, Specification By Examples, User Story Mapping, Impact Mapping. Presentation cover starting from Product Vision till Product Increment and living document. Behavior Driven Development using Gherkin, Cucumber, Java and Junit
DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, our model indicates concrete activities rather than general statements.
Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
In the session, it is planned to demonstrate “DevOps Tactical Adoption Theory” with focus on Delivery Pipeline/Testing Practices sectioned "Continuous Testing in DevOps".
Shift left, shift right the testing swing.
This deck shows the testing framework we use today in our agile & Devops team. We do Behavior Driven Development (Shift left) and test in production as well (shift right).
Inverting Test Pyramid - A First Hand Experience ReportNaresh Jain
Test automation is extremely crucial in adoption of an agile delivery. However, it can take one for a ride, if the approach is not correct. In this sensational, heart throbbing, experience report, we'll share our story of how we turned around an inefficient, expensive automation style to lean, efficient style. In addition to sharing a real-world example, we'll also share some of the key challenges we faced and how we solved them. If you are convinced about the Testing Pyramid, but are struggling to invert it, then this session is for you.
Business Impact:
* Earlier Defect Detection - Higher test coverage at Unit/Intermediate layers lead to earlier defect detection. Reduced number of issues found on higher test environments/Production. Reduced cost of defect fixing.
* Reduced maintenance cost - UI tests are fragile and costlier to maintain Vs backend tests. No of changes in services layer are comparatively less.
Reduced test execution time - Backend tests are much faster. Almost 7-10 times faster than UI Tests - improved build certification time.
* Test feedbacks are naturally distributed across layers of application. Test feedbacks are more pin pointed/ granular.
Details: http://confengine.com/agile-pune-2014/proposal/471/inverting-test-pyramid-a-first-hand-experience-report
Conference: http://pune.agileindia.org/
From the the teams struggling with DevOps to experienced professionals trying to make a shift to DevOps, this presentation helps in how understanding how DevOps makes Deliveries faster and accurate
DevOps – the future of Agile – why, what, how? Agile Israel 2014Yuval Yeret
DevOps is the new favorite buzzword in many organizations. We will understand what it is all about, why it is necessary and what makes it so popular, how it is related to Agile, some pitfalls/myths, and most importantly some concrete steps organizations can take to become a more DevOps-oriented organization and enjoy benefits like more frequent less painful software deployments and operation and better collaboration between Dev and Ops organizations.
http://agileisrael2014.com/devops-the-future-of-agile/
In many organizations, agile development processes are driving the pursuit of faster software releases, which has spawned a set of new practices called DevOps. DevOps stresses communications and integration between development and operations, including continuous integration, continuous delivery, and rapid deployments. Because DevOps practices require confidence that changes made to the code base will function as expected. automated testing is an essential ingredient Join Jeff Payne as he discusses the unique challenges associated with integrating automated testing into continuous integration/continuous delivery (CI/CD) environments. Learn the internals of how CI/CD works, appropriate tooling, and test integration points. Find out howpto integrate your existing test automation frameworks into a DevOps environment and leave with roadmap for integrating test automation with continuous integration and delivery.
Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony
Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions:
- Who are the people I need in place?
- What are the core processes that I need to change?
- What tools do I need?
View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar
Behavior driven development - Deliver Value by CollaborationNaveen Kumar Singh
BDD, Specification By Examples, User Story Mapping, Impact Mapping. Presentation cover starting from Product Vision till Product Increment and living document. Behavior Driven Development using Gherkin, Cucumber, Java and Junit
DevOps Tactical Adoption Theory tries to make the transition process as smooth as possible. It hypothesis each step towards DevOps maturity should bring a visible business value empowering management and team commitment for the next step. The innovative idea here, it is not required to add the tools/processes to stack from sequential beginning to end, but seeking benefit.
The reason behind the theory is to encourage practitioners to apply each step one-by-one and then having the benefits in projects. Consequently, each step is tested in terms of utility and proved method validity for the further steps. In contrast to previous adoption models, our model indicates concrete activities rather than general statements.
Theory built on the claim that many DevOps transition projects considered problematic, impractical or even unsuccessful causing concept to become a goal more than a technique. Basically, theory consists of different areas of interest describing various actions on a schema.
In the session, it is planned to demonstrate “DevOps Tactical Adoption Theory” with focus on Delivery Pipeline/Testing Practices sectioned "Continuous Testing in DevOps".
Continuous Testing: A Key to DevOps SuccessTechWell
As IT organizations adopt a DevOps strategy, continuous testing (CT) becomes a key ingredient of the DevOps ecosystem. CT enables faster release cycles, more changes per release, upfront isolation of risks, and reduced operations costs. The approach to scale the traditional automation testing infrastructure, test environments, and test data management requires a culture shift using new tools and techniques. Sujay Honnamane discusses a CT strategy for aspiring and already implemented DevOps organizations. Sujay shares examples of tools, techniques, and practical solutions that include continuous integration using the Jenkins CI server, service virtualization through CA Lisa tools, automated code coverage analysis to create impact-based tests, automated test script load balancing for effective use of test environments, and faster test cycles, providing a holistic approach/workflow for CT. Sujay and his teams have successfully implemented CT for several clients in their DevOps journey to achieve a repeatable and highly predictable software delivery process.
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
DOES14 - Jonny Wooldridge - The Cambridge Satchel Company - 10 Enterprise Tip...Gene Kim
Jonny Wooldridge, CTO, The Cambridge Satchel Company at the DevOps Enterprise Summit 2014
View video: https://www.youtube.com/watch?v=CzUTztwcc58
View Jonny Wooldridge's blog: http://www.enterprisedevops.com
Following 3.5 years building a DevOps capability and culture at M&S I will be condensing the experience down to 10 Enterprise DevOps tips that are relevant to companies of all sizes and complexities. Bringing start-up lean thinking to an enterprise was never going to be easy but the lessons learned are relevant to us all.
BizDevOps – Delivering Business Value Quickly at ScaleQASymphony
BIZDEVOPS – DELIVERING BUSINESS VALUE QUICKLY AT SCALE
65+% of surveyed organizations are currently on the path to switch to DevOps or have already implemented the process, and the benefits of a properly implemented DevOps program are clear – quicker time to customer value, better alignment between businesses and customers, and a better ability to respond to customer input. However, when it comes to DevOps adoption, many teams rush to focus on one specific issue within one area when they would actually benefit more from aligning business, development, testing, and operations up front. The five major problems in DevOps adoption include:
Lack of Test Automation Coverage
Lack of Visibility into Testing
Maintaining Various Test Versions and Aligning Tests with Versions of Source Code
Maintaining a Single Source of Truth in the Testing Process
Understanding Where Business Value Currently is in the “BizDevOps” Pipeline
After helping hundreds of customers in their DevOps journeys, these three industry experts will cover these major problems, as well as innovative strategies to overcome them:
Bobby Smith – Director of R&D, QAS Labs
Brandon Cipe – VP DevOps, cPrime
Kevin Dunne – VP Business Development, QASymphony
Tune in to learn more about the state of the industry, the direction that DevOps adoption is moving toward, and what we like to call “BizDevOps”. You won’t want to miss this session!
Mind the Gap: How to bridge the gap between development and operations with release management
The release management process remains challenging for large IT organizations due to the continuing disconnect between development, QA, and operations teams. The challenge faced by these large enterprises is that process maturity, methodology, and platforms vary greatly across teams, organizations and business units. These challenges often produce gaps between development and operations teams. Release management is still being done, but with very inconsistent results and at a high cost, providing minimal insight and a lack of audit compliance.
Join us as Julian Fish, Director of Products at Serena Software, demonstrates how the unique integration framework and process capabilities of Serena Release Control can deliver a consistent and repeatable process that provides complete traceability, audit and compliance across Waterfall, Progressive and Agile processes, for both ITIL and DevOps approaches, and supporting Mainframe to mobile platforms.
For a beginner, this is a good quality pictorial representation of DevOps and DevOps Center of Excellence.
Opex Software focuses on consulting, implementation and development of DevOps tools and platforms. Have helped small and large data centers! This presentation talks about Continuous Integration, Continuous Delivery at a high level. For detailed presentations and flows, please ping us.
Thanks again, Enjoy!
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENTIndium Software
IP-led test automation framework supported by blueprint
for product development in Devops environment can
ensure automation in the true sense.
DevOps is fast becoming adopted as the environment for product
development. It facilitates closer integration of development and operations
teams, reducing the time needed to develop and deploy a product. However,
it is still in its early stages and the teams continue to work in silos due to the
different kinds of tools they need suited to their needs.
An IP-driven testing framework like iSAFE can be the bulwark on which the development, testing and operations teams can integrate more seamlessly,
as it provides one key feature needed when handling such a comprehensive
environment – traceability. The other advantages, of course, are reusability,
automated alerts and shorter testing periods, thus aiding in the quick time-to-market
needs of the organizations.
Software development (Dev) and IT operations (Ops) are the roots of the term "DevOps" (Ops). The term refers to a culture change that will enable the continuous delivery of high-quality software and reduce the development cycle. It is primarily distinguished by shared ownership, automated workflow, and quick feedback principles. As a result, all phases of the software development cycle, not just a few, must be understood by the team members.
Agile testing is the soware testing
methodology that stems from the Agile
soware development principles. The
essence of Agile testing practice is that it
incorporates testing into the dev process,
rather than keeping it a separate SDLC
phase.
Be agile. Scale up. Stay Lean with SAFe by Michael StumpAgile ME
Today’s successful companies are recognizing that software is increasingly a competitive advantage for their business. Real, tangible software development value occurs only when end-users are successfully operating the software in their environment. To ensure a faster flow of value to the business, the Scaled Agile Framework helps teams successfully deliver a differentiated and engaging customer experience, achieve quicker time to value, and gain increased capacity to innovate. The process of deploying software builds to production is no less important than developing and testing the new functionality. As an industry, we are currently mastering more Agile, better and faster methods for incrementally developing potential user value. In practice, however, these achievements are jeopardized by poorly managed deployments that happen too late in the lifecycle and delays value delivery. Bringing deployment operations (DevOps) onboard the Agile Release Train, engaging them in the PSI planning and other program level events, and establishing environments, practices and disciplined procedures in support of a continuous deployment pipeline helps the enterprise enable faster feedback and a more predictable value delivery rhythm. Join Michael Stump (Principal Contributor to SAFe), Thought Leader from Scaled Agile Inc. and software industry veteran to get an in-depth overview of how SAFe together with DevOps can provide the most customer value and quality in the sustainable shortest lead time.
The Definitive Guide to Implementing Shift Left Testing in QARapidValue
In today's digital world, even though most of the projects are following the Agile methodology, often testers might not get enough time to quantify the problem scope and test the product effectively. Even if a sprint lasts for two weeks, the QA team would get the complete functionality for testing, only two or three days before the sprint completion. Eventually, the QA team would have to rush the testing, struggle for test completion and even end up with improper test coverage and bugs being leaked into production. So the testing phase is often considered as a bottleneck for the release by the management.
Studies done by analysts suggest that the maximum number of defects occur during the requirement
and design phase of the software development life cycle. More than half of the defects occur during the
requirement and design phase of the SDLC, i.e 56% of the total defects. Out of this 56%, 23% occurs during the design phase, 7% in the development phase and 10% defects emerge during the other phases. 2019 witnessed test automation going mainstream with 44% of IT organizations automating more than 50% of
all testing and these figures are expected to go up in the upcoming years. Thus it becomes highly necessary to step up the testing game and ensure that it is done quite efficiently and this is where Shift Left Testing comes into play. Detecting defects early in the software development cycle can prove to be very crucial in regards to cost and efficiency.
This whitepaper discusses how shift left testing could help you reimagine the entire QA testing process.
First DRAFT of a DevOps presentation and posters covering the essentials for a DevOps mindset. Help improve the content by forking and contributing a pull request to https://github.com/wpschaub/DevOps-mindset-essentials/blob/master/README.md.
my understanding of fundamentals of DevOps and how it relates conceptually to Agile, Scrum, Kanban, etc.
SlideShare does not allow uploading a new version of existing presentation. Hence I have to upload the new verson.
Goto https://www.slideshare.net/nitinbhide/devops-understanding-core-concepts for latest version.
I recently did a talk on Agile and the importance of people over role/process obsessions. I didnt use this in the end, as I decided to adopt a more natural and example-based approach. Feel free to use however - the web is built on plagiarism after all ;)
Similar to EuregJUG 2016-01-07 - Swimming upstream in the container revolution (20)
Multi-cluster Kubernetes Networking- Patterns, Projects and GuidelinesSanjeev Rampal
Talk presented at Kubernetes Community Day, New York, May 2024.
Technical summary of Multi-Cluster Kubernetes Networking architectures with focus on 4 key topics.
1) Key patterns for Multi-cluster architectures
2) Architectural comparison of several OSS/ CNCF projects to address these patterns
3) Evolution trends for the APIs of these projects
4) Some design recommendations & guidelines for adopting/ deploying these solutions.
ER(Entity Relationship) Diagram for online shopping - TAEHimani415946
https://bit.ly/3KACoyV
The ER diagram for the project is the foundation for the building of the database of the project. The properties, datatypes, and attributes are defined by the ER diagram.
This 7-second Brain Wave Ritual Attracts Money To You.!nirahealhty
Discover the power of a simple 7-second brain wave ritual that can attract wealth and abundance into your life. By tapping into specific brain frequencies, this technique helps you manifest financial success effortlessly. Ready to transform your financial future? Try this powerful ritual and start attracting money today!
1.Wireless Communication System_Wireless communication is a broad term that i...JeyaPerumal1
Wireless communication involves the transmission of information over a distance without the help of wires, cables or any other forms of electrical conductors.
Wireless communication is a broad term that incorporates all procedures and forms of connecting and communicating between two or more devices using a wireless signal through wireless communication technologies and devices.
Features of Wireless Communication
The evolution of wireless technology has brought many advancements with its effective features.
The transmitted distance can be anywhere between a few meters (for example, a television's remote control) and thousands of kilometers (for example, radio communication).
Wireless communication can be used for cellular telephony, wireless access to the internet, wireless home networking, and so on.
3. Outline
S o w h a t ‘ s n e x t ?
Approach
Principles
Introduction
Definitions
Challenges
and
lessons
learned
Business
benefits
Looking
ahead
4. Every
change
goes
through
the
build/test
pipeline
and
automatically
gets
put
into
production.
Continuous Deployment
Development
and
operations
engineers
participate
together
in
the
entire
product
lifecycle
-‐
and
are
responsible
together
for
the
product.
DevOps
Building
and
testing
software
in
such
a
way
that
the
software
can
be
released
to
production
at
any
time.
"Ship
early,
ship
often,
sacrificing
features,
never
quality"
-‐
Kyle
Neath
Continuous Delivery
Team
members
integrate
their
work
frequently.
Commits
are
verified
by
automated
builds
and
tests.
Continuous Integration
Definitions
Who’s
who
in
DevOps
5. Malmberg
is
an
educational
publisher
in
the
Netherlands.
Malmberg
is
building
modern,
rich
and
scalable
e-‐learning
applications
using
Java
8,
Vert.x,
AngularJS
and
MongoDB,
running
on
Amazon
cloud
services.
About Malmberg
6.
7. Differences lead to issues
Communication between development
and operations was slow, problem
analysis in production was difficult and
releases took a lot of time.
Traditional operations
Production environments managed
by external operations partner.
Differences in infrastructure between
development and production.
Modern development culture
Modern tools, lots of automation.
Test environments are managed
by developers.
History
About
a
year
ago
Things needed to change
Issues and differences between
development and operations were
slowing us down. We needed to shift
strategies to keep progressing.
8. …said no product manager ever.
J.
Paul
Reed
Let’s spend the next few months..
..working
on
automated
testing
and
build/release
infrastructure,
and
redesigning
how
our
application
is
written.
We
can
postpone
our
feature
development.
“
”
9. Build a complete new setup to
allow development teams to
transform to the new
situation at their own pace.
Keep the shop open
Build a dedicated team of
Devs, Ops and Cloud experts.
Expert team
Define key points that identify
your approach and help you
set goals.
Define principles
Approach
How
we
initiated
change.
11. Master branch is always releasable
Principle 1
Every change is developed and tested in a feature branch.
Don’t merge it until it’s done.
12. Unit/integration (Java & JavaScript), mutation, end-to-end (FitNesse/BrowserStack),
performance (Gatling), layout (Galen), Sonar for quality and coverage reporting.
Rely on multiple layers of tests.
Each commit is tested extensively
Principle 2
13. Manage builds, tests, QA and deployments from a single place.
Jenkins as the heart of the delivery process.
Every delivery step is a Jenkins job
Principle 3
14. After deploying 6 new features, when one has an issue, why roll back 5 good features?
Don’t. Just roll out a fix quickly.
Keep moving ahead.
Deployments are roll-forward only
Principle 4
15. No logging in to servers. Need a change or upgrade? Just update the server recipe.
Hands off.
Infrastructure as code - for everything
Principle 5
16. The flexibility and resilience is well worth it.
So how about using containers? The EC2 instance is our container.
Even when you don’t need to scale… yet.
Put everything in auto scaling groups
Principle 6
17. You can’t explain maintenance windows to modern end users anymore.
Our end users are the Facebook generation.
No downtime in production
Principle 7
18. Make sure you find the problem before it finds you.
Work proactive, not reactive.
Eyes and ears in production
Principle 8
19. Repeating tasks such as viewing logs and doing deployments must be common jobs.
Specialisms are OK, but only for incidental tasks.
Repeating tasks are executable for all team members
Principle 9
20. Differences between teams are OK. A team that’s dependent on external help is not.
Give teams the freedom to work in a way that works for them.
DevOps teams work on a self service basis
Principle 10
21. Challenges
01
When you automate everything and
keep growing, chances are you’re
going to hit limits.
Amazon has limits
04All environments are provisioned
automatically. Challenge: how to
prevent testing directly in
production.
How to test Puppet changes
Not all developers are comfortable
with managing infrastructure and
middleware.
Devs need to step up their game
06
When transforming an organisation,
you need to be really clear about
where things are going, why things
are happening and when this will
impact teams.
Communication is key
03
Don't assume that cultural change
won't be an issue. It will.
Resistance02
This kills team progress.
Don’t depend on availability
of Ops experts
05
and
lessons
learned
22. Auto scaling and pro-active monitoring
boost availability. A lot.
Availability
Business benefits
High level of automation results in
shorter release cycles and faster time to
market.
Agility
Automated provisioning makes sure that
every environment can be re-built from
scratch in minutes.
Continuity
Lower operations costs due to scheduling
and scaling. Lower maintenance costs due
to high degree of automation.
Cost reduction
Faster problem analysis and solution.
Better reaction speed
How to sell this to your boss.
23. Get
the
teams
the
information
they
need,
readily
available
on
a
dashboard
visible
from
their
desks.
Better monitoring and dashboards
Looking ahead
01
There
is
no
silver
bullet
here,
but
useful
tools
and
practices
do
exist.
Continuous security testing03
Daily
performance
runs
on
test
environments
and
continuous
end-‐user
performance
monitoring
in
production.
Continuous performance testing02
The
only
way
to
be
really
prepared
for
failure
is
to
make
sure
that
things
will
fail
by
breaking
it
yourself.
Automated resilience testing04
Stuff we’re still working on