GOVERNMENT POLYTECHNIC, AURANGABAD

(An Autonomous Institute of Government of Maharashtra)

SEMINAR REPORT

ON

“Ethical Hacking”
SUBMITTED BY-

MOHAMMAD YASEEN MOHAMMAD AKBAR

(214023)

GUIDED BY-

PROF. D. S. SONWANE

(H.O.D, AIML)

ACADEMIC YEAR 2023-24

DEPARTMENT

OF

ARTIFICIAL INTELLIGENCE AND MACHINE LEARNING

 Page |2

GOVERNMENT POLYTECHNIC, AURANGABAD

(An Autonomous Institute of Government of Maharashtra)

CERTIFICATE

This is to certify that Mohammad Yaseen Mohammad Akbar has successfully

completed seminar regarding topic “Ethical Hacking” during the academic year
2023-2024, in partial fulfilment of Diploma in AIML of Government Polytechnic,
Aurangabad. To the best of my knowledge and belief this seminar work has not been
submitted elsewhere.

Date:- / /2023

Prof. D. S. Sonwane Prof. D. S. Sonwane

SEMINAR GUIDE H. O. D. AIML

DR. A. M. Jinturkar

Principle
 Page |3

AKNOWLEDGEMENT

I have taken an immense pleasure in thanking DR. A. M. Jinturkar, the principal,

Government Polytechnic, Aurangabad, our source of inspiration. We wish to express
our deep sense of gratitude to Mr. D. S. Sonawane, our respected Head of Department
Artificial Intelligence and Machine Learning, and Mr. D. S. Sonawane, my guide for
having permitted us to carry out this seminar under his valuable guidance and useful
suggestions, which have helped us in completing the seminar in time.

I would also like to thank to all our faculty members of our department for their
valuable suggestion in the process of this project work. Finally, yet importantly, I
would like to express our thanks to our beloved parents for their blessings. Last but
never the least; let us thanks our friends and classmates for their help and co-operation
for the successful completion of this seminar.

Mohammad Yaseen Akbar

(Enrolment No.- 214023)

 Page |1

Abstract

Today more and more software are being developed and people are getting more
and more options in their present software ‘s. But many are not aware that they are
being hacked without their knowledge. One reaction to this state of affairs is a
behaviour termed ―Ethical Hacking" which attempts to pro-actively increase security
protection by identifying and patching known security vulnerabilities on systems
owned by other parties.

A good ethical hacker should know the methodology chosen by the hacker like
reconnaissance, host or target scanning, gaining access, maintaining access and
clearing tracks. For ethical hacking we should know about the various tools and
methods that can be used by a black hat hacker apart from the methodology used by
him.

From the point of view of the user one should know at least some of these
because some hackers make use of those who are not aware of the various hacking
methods to hack into a system. Also, when thinking from the point of view of the
developer, he also should be aware of these since he should be able to close holes in
his software even with the usage of the various tools. With the advent of new tools, the
hackers may make new tactics. But at least the software will be resistant to some of the
tools.
 Page |2

INDEX

Sr. No. Contents Page No.

Abstract 1

1. Introduction 3
1.1 What is Ethical Hacking? 4
1.1.2 Why Ethical Hacking Matters. 4
1.1.2 Who Are Ethical Hackers 5
2. History Of Ethical Hacking 6
2.1 Early Era of Ethical Hacking 7
2.2 The Emergence of Ethical 7
3. Different Types of Hackers 8
4. Why Ethical Hacking is Required? 10
5. The Process of Ethical Hacking? 12
5.1 Hacking at Different Phases of Its cycle
6. Different Tools Used in Ethical Hacking 14

7. Advantages of Ethical Hacking 19

8. How does DevOps compare to traditional development 22
methods?
8.1 How efficient are the development cycles? 23
8.2 How do they manage scheduling? 24
9. Challenges and Solutions with real life examples 25
9.1 Amazon 26
9.2 HP 27
9.3 Etsy 28
10. The Future of DevOps: Possibilities and Challenges 32
10.1 Based on industry 33
10.2 Based on location 34
 Conclusion 36
 Page |3

INDEX

Sr. No. Contents Page No.

Abstract 1

1. Introduction 3
1.1 What is Ethical Hacking? 4
1.1.2 Why Ethical Hacking Matters. 4
1.1.2 Who Are Ethical Hackers 5
2. History Of Ethical Hacking 6
2.1 Early Era of Ethical Hacking 7
2.2 The Emergence of Ethical 7
3. Different Types of Hackers 8
4. Why Ethical Hacking is Required? 10
5. The Process of Ethical Hacking? 12
5.1 Hacking at Different Phases of Its cycle
6. Different Tools Used in Ethical Hacking 14
7. Advantages of Ethical Hacking

8. Disadvantages of Ethical Hacking

9.
 Page |4

1.Introduction

DevOps is a term for a set of concepts that, while not all new, have catalyzed into a
movement and are rapidly spreading throughout the technical community. The term
DevOps is derived from software development and IT Operations. It’s not just about
containers or tools like Kubernetes. DevOps is about thinking critically about how
your organization works, who does what work, and when things should happen—and
then making it happen.

Top concerns that we hear from customers are “How can we release on-time?”,
“How can we have a stable release?” or “How can we address the problems before end
users get impacted?” Happiest Minds answer them in a simple one-liner, “Embrace
DevOps”. Whether you are a tiny startup, a mid-sized one or a Fortune 500 company,
be informed that the IT industry is adopting DevOps at an amazing pace.

Even then, majority of IT professionals either don’t know about DevOps or just
have a partial understanding of the big picture. At Happiest Minds, we see DevOps as
a business driven software delivery approach, an approach that takes a new or
enhanced business idea from design to development to testing and all the way to
production, providing business value to customers in an efficient manner.

A process of introduction of the DevOps practices in a production system is

presented. The DevOps technique was introduced to improve the collaboration of the
Development with the Operations using continuous methods for improving software
development process. Some elements used in DevOps are gradually introduced to the
waterfall lifecycle. It is shown that it is possible to benefit from the DevOps approach
in all of them even if it proceeds in stages.

The improvement to the software implementation and delivery is a long process ,

but it can be measured based on some metrics (i.e. number of user stories, a number of
releases per year). The results will be described and compared with the situation before
the DevOps aspects have been introduced .Whether you are a tiny startup, a mid-sized
one or a Fortune 500 company, be informed that the IT industry is adopting DevOps at
an amazing pace. Even then, majority of IT professionals either don’t know about
DevOps or just have a partial under-standing of the big picture.
 Page |5

1.1What is DevOps?

1.1.1 Definition

DevOps (a portmanteau of “development” and “operations”) is the combination of

practices and tools designed to increase an organization’s ability to deliver applications
and services faster than traditional software development processes. This speed enables
organizations to better serve their customers and compete more effectively in the
market.

In simple terms, DevOps is about removing the barriers between traditionally siloed
teams, development and operations. Under a DevOps model, development and
operations teams work together across the entire software application life cycle, from
development and test through deployment to operations.

fig.1.1 logo of DevOps

1.2.1 Simplification

DevOps can be best explained as people working together to conceive, build and
deliver secure software at top speed. DevOps practices enable software development
 Page |6

(dev) and operations (ops) teams to accelerate delivery through automation,

collaboration, fast feedback, and iterative improvement.
Stemming from an Agile approach to software development, a DevOps process
expands on the cross-functional approach of building and shipping applications in a
faster and more iterative manner. In adopting a DevOps development process, you are
making a decision to improve the flow and value delivery of your application by
encouraging a more collaborative environment at all stages of the development cycle.

DevOps represents a change in mindset for IT culture. In building on top of Agile,

lean practices, and systems theory, DevOps focuses on incremental development and
rapid delivery of software. Success relies on the ability to create a culture of
accountability, improved collaboration, empathy, and joint responsibility for business
outcomes.

fig.1.2 DevOps in IT

DevOps is a set of practices, principles, and cultural philosophies that promote

collaboration and communication between software development and IT operations
teams. It aims to automate and integrate the processes of software development,
testing, and deployment to achieve faster and more reliable software releases.

DevOps emphasizes a culture of shared responsibility, continuous integration,

continuous delivery, and close collaboration between different teams involved in the
software development lifecycle.
 Page |7

2. Literature Survey

The origins of the DevOps trace back to when the term, “DevOps” was first coined
by Patrick Debois in 2009 which is regarded as the DevOps origin year. Debois is now
regarded as one of the pioneering figures of DevOps and has gained significance over
the years as one of its gurus with more and more organizations integrating DevOps
into their operating systems. To answer the looming question of when DevOps started,
let us first look at how the term was formulated. The evolution of DevOps occurred
because of the combination of the words “development” and “operations,”. This,
therefore essentially provides a fundamental point for comprehending what exactly
people mean when they refer to “DevOps.” One important thing you need to know
about the DevOps methodology is that it isn’t a technology, process or established
definitive.

DevOps is often referred to as a cultural viewpoint. Most importantly, the true

meaning of DevOps has widened to become an umbrella term referring to the culture,
processes, and mindset used for optimizing and shortening the life cycle of software
development with the help of fast feedback loops for offering features, updates and
fixes at a frequent pace. To know more about the DevOps culture and find the answer
to the question ‘when did DevOps start?’, you can check out some of the Best DevOps
Courses online to help you acquire a comprehensive idea about what it is, how it
functions and how it is implemented.

The DevOps history is quite an interesting one considering how it was first
implemented into the workflow systems of organizations at large. In this article, we
will discuss in detail when DevOps started, and the detailed history and evolution of
DevOps.

2.1 Bringing development and IT teams together

The DevOps movement started to coalesce some time between 2007 and 2008, when
IT operations and software development communities raised concerns what they felt
was a fatal level of dysfunction in the industry.
 Page |8

They railed against the traditional software development model, which called for
those who write code to be organizationally and functionally apart from those who
deploy and support that code.

Developers and IT/Ops professionals had separate (and often competing) objectives,
separate department leadership, separate key performance indicators by which they
were judged, and often worked on separate floors or even separate buildings. The
result was siloed teams concerned only with their own fiefdoms, long hours, botched
releases, and unhappy customers. Surely there’s a better way, they said. So, the two
communities came together and started talking – with people like Patrick Debois, Gene
Kim, and John Willis driving the conversation.

What began in online forums and local meet-ups is now a major theme in the
software zeitgeist, which is probably what brought you here! You and your team are
feeling the pain caused by siloed teams and broken lines of communication within
your company.

2.2 How it is before DevOps?

Before we go into the detailed DevOps history, let us take a prime example of a
platform that deploys daily; Netflix. As modern consumers of entertainment, we can
never imagine a world where Netflix only deploys once a month or every few months.
This was the sad state of affairs for developers back in the day when they followed the
old waterfall methodology.

As per the brief history of DevOps, the deployment of software, it was first
developed and thoroughly tested for months prior to their release in the market. Up till
the date of release, the QA would be hustling to test everything and return defects,
while devs would be hustling in bug fixing and sending them faster to the QA so that
they could run them through tests. The night prior to the release, the QA and Ops
would often ask management to postpone the release date due to the software not being
production-ready.

The business stakeholders were a completely different story on the other hand. They
would push them to stick to the predestined plan. The software would further be
deployed but would go through either of the tow:-
 Page |9

It would either be rolled back in the following 12 hours after everyone would exhaust
their options trying to make everything work

It would reach the stage of production and for the following weeks, the Ops team
would perform rolling restarts, hotfixes, and everything possible to reduce the impact.

3. Why DevOps is required?

Now that we have defined DevOps, we must go beyond and analyze the reasons for
companies to adopt this methodology. Before we discuss such motives, it might be
interesting to point out that, according to DevOps.com, the number of companies that
have incorporated DevOps has been increasing exponentially every year.

The “automate everything” mindset of DevOps can certainly transform

productivity levels. But not everything can be automated: Failure to understand the
context, overlooking important actions because of communication barriers and poor
collaboration are some of the human factors that stop DevOps being a silver bullet.
But it can be an effective weapon if you combine the right technology with the
right culture, attitude and skill sets.

The reasons that have contributed the most to DevOps’ development are:
 P a g e | 10

fig. 3.1 Dev And Ops Team

1. Shorter development cycles that encourage innovation

The fact that both departments (development and operations) come together is an
advantage when it comes to releasing new apps, products… It is generally known that
the more innovative companies are, the higher their chances of outrunning the
competition. Which is essential to increase significantly competitiveness.

2. More collaboration, better communication

Thanks to the union between both teams, productivity improves a lot. The
DevOps culture is based on achieving the best performance in such a union, instead of
worrying about individual objectives. As a result of both departments being fused, the
process becomes more fluid since everyone is oriented towards a common goal.

To ensure that your DevOps team reaches its best performance, it is necessary to
create a transparency culture in which responsibilities are shared and immediate
feedback is guaranteed.-Microservices: everything you need to know-

3. Reduced deployment failures and faster time to recover

Most failures during development occur due to programming defects. Having a

DevOps team will allow for more releases in shorter time spawns. This way, it is easier
and more likely to find possible defects in the code. For this same reason, and in case
any problem must be solved, recovery will be quicker thanks to the knowledge and
participation of all members during the development process.

4. Efficiency: Improved resource management

Increased efficiency helps speed up development and reduce coding defects and
problems.Nowadays, some programs are capable of automating DevOps tasks,
reducing, as a result, the need for manual labor. What does this mean? Simply put, that
software engineers can concentrate more on the kind of tasks that cannot be automated.

Companies that have transitioned to more automated DevOps processes have been
able to adapt more successfully to the global upheaval caused by Covid-19,
whereas those with legacy pipelines and no DevOps instrumentation processes tend
to have struggled. Now, many are rushing to get the right tools and process in place
not to mention the major cultural changes required to make DevOps successful.
 P a g e | 11

4.DevOps Methodologies

DevOps is the direct descendant of agile software development, born from the need
to keep up with increased software development velocity and throughput agile
methods. Advancements in agile development highlighted the need for a more holistic
approach to the software delivery life cycle, resulting in DevOps.

fig.4.1Software development evolution

“Agile development” is an umbrella term for several iterative software development

methodologies, many of which have carried over to DevOps:

Scrum—

a framework in which people can address complex adaptive problems while delivering
products of the highest possible value.
 P a g e | 12

Kanban—

a method for managing the creation of products with an emphasis on continual

delivery while not overburdening the development team. Like Scrum, Kanban is a
process designed to help teams work together more effectively.

Scaled Agile Framework (SAFe)—

a set of organization and workflow patterns intended to guide enterprises in scaling

lean and agile practices. SAFe is one of a growing number of frameworks that seek to
address the problems encountered when scaling beyond a single team.

Lean development-

a translation of lean manufacturing principles and practices to the software

development domain. Lean offers a conceptual framework, values, and principles, as
well as best practices derived from experience, that support agile organizations.

Extreme programming (XP)

—a software development methodology intended to improve software quality and

responsiveness to changing customer requirements. XP advocates frequent releases in
short development cycles, intended to improve productivity and introduce checkpoints
at which new customer requirements can be adopted. Other elements of extreme
programming include programming in pairs or doing extensive code review, unit
testing of all code, not programming of features until they are needed, a flat
management structure, code simplicity and clarity, expecting changes in the customer’s
requirements as time passes and the problem is better understood, and frequent
communication with the customer.
 P a g e | 13

Fig.4.2Agile to devOps

5.What are the 6 C’s of DevOps processes?

Its practices lead to high productivity, minor bugs, improved communication, enhanced
quality, faster resolution of problems, more reliability, better and timely delivery of
software.

1. Continuous Integration
2. Continuous Testing
3. Continuous Delivery
4. Continuous Deployment
5. Continuous Monitoring
6. Continuous Business Planning

fig.5.1 Diagram demonstrating benefits

Continuous Integration

It means isolated changes are tested and reported when they are added to a
larger codebase. Continuous integration aims to give rapid feedback so any defect can
be identified and corrected immediately. Jenkins is used for continuous integration,
which follows 3 step rule, i.e., build, test, and deploy. Here developer makes frequent
changes to the source code in the shared repository several times a day. Along with
 P a g e | 14

Jenkins, we have more tools, too, i.e., BuildBot, Travis, etc. Jenkins widely used
because it provides plugins for testing, reporting, notification, deployment etc.

Continuous Testing

Continuous Testing obtains immediate feedback on the business risk associated

with Software Releases. It's a challenging and essential part of the software. Software
rating depends upon Testing. The test function helps the developer to balance quality
and speed. Automated tools are used for testing as it is easier to test continuously than
testing a full software. The tool used for testing the software is Selenium.

Continuous Delivery

It is the ability to do changes like including new features, configuration

management, fixes bugs and experiments into production. Our motive for doing
continuous delivery is a continuous daily improvement. If there is an error in the
production code, we can quickly fix it at that time. So, here we are developing and
deploying our application rapidly, reliably and repeatedly with minimum overhead.

Continuous Deployment

The code is automatically deployed to the production environment as it passes

through all the test cases. Continuous versioning ensures that multiple code versions
are available in the proper places. Here every changed code is put into production,
automatically resulting in many deployments in the production environment every day.

Continuous Monitoring

It is a reporting tool because of which developers and testers understand the

performance and availability of their application, even before it is deployed to
operations? Feedback provided by continuous monitoring is essential for lowering the
cost of errors and change. Nagios tool is used for continuous monitoring.

Now, these are the 6C’s of DevOps processes.

 P a g e | 15

6. Different phases of the DevOps Lifecycle

DevOps Lifecycle is a methodology software development teams use to bring

products to market more quickly and efficiently. It's a way of managing the entire
software lifecycle from development through release, focusing on collaboration
between developers and IT operations professionals. Constant software creation,
development, verification, release, and management are part of the DevOps
lifecycle.

The DevOps strategy supports innovative thinking, speed, and adaptability to

produce, verify, utilize, and develop software applications. To innovate goods,
services, and operations, encourages a spirit of innovation, review, and continuous
improvement. To adopt DevOps, though, a thorough grasp of the various stages of
the DevSecOps lifecycle is required.

Here is the phases of DevOps-

Plan-

Professionals determine the commercial need and gather end-user opinions throughout
this level. In this step, they design a project plan to optimize business impact and
produce the intended result.

Code –

During this point, the code is being developed. To simplify the design process, the
developer team employs lifecycle DevOps tools and extensions like Git that assist
them in preventing safety problems and bad coding standards.

Build –

After programmers have completed their tasks, they use tools such as Maven and
Gradle to submit the code to the common code source.
 P a g e | 16

Test –

To assure software integrity, the product is first delivered to the test platform to
execute various sorts of screening such as user acceptability testing, safety testing,
integration checking, speed testing, and so on, utilizing tools such as JUnit, Selenium,
etc.

Release –

At this point, the build is prepared to be deployed in the operational environment. The
DevOps department prepares updates or sends several versions to production when the
build satisfies all checks based on the organizational demands.

Deploy –

At this point, Infrastructure-as-Code assists in creating the operational infrastructure

and subsequently publishes the build using various DevOps lifecycle tools.

Operate –

This version is now convenient for users to utilize. With tools including Chef, the
management department take care of server configuration and deployment at this
point.

Monitor –

The DevOps workflow is observed at this level depending on data gathered from
consumer behavior, application efficiency, and other sources. The ability to observe the
complete surroundings aids teams in identifying bottlenecks affecting the production
and operations teams’ performance.
 P a g e | 17

fig.6.1 DevOps Tools

6.1 DevOps Toolchain

DevOps is a methodology that aims to optimize the process of software

development and operation. It is an approach that helps organizations produce
software products and services faster while meeting customer expectations.

Everything in DevOps is ongoing, from strategy to maintenance, as we mentioned

previously. Now, let's split out the entire lifespan into seven stages, using stability
as the focus. Every DevOps life cycle phase can repeat several times across the
program until it is completed. The goal is to create an environment where code can
move quickly through the pipeline while maintaining high-quality levels.

A DevOps toolchain includes the tools and technology that enable development and
operations teams to collaborate across the entire software lifecycle. It tackles key
DevOps fundamentals including continuous integration, continuous delivery,
automation, and collaboration.
 P a g e | 18

fig.6.2 different platforms

Collaboration-

The greatest catch of the DevOps culture is collaboration and communication between
different teams. Different teams like development, testing, and product coordinate and
work to automate this entire process. Collaboration tools help teams work together
regardless of time zones and locations. Faster communication means faster software
releases. A few examples of collaboration tools are Slack, Campfire, and Skype.

Planning-

Stakeholders, clients, and employees working with different teams should have
common goals. Therefore, transparency among all participants is important. Planning
tools provide this transparency. A couple of examples of planning tools are Asana and
Clarizen.

Source Control-

You need a centralized storage location for all your data, documentation, code,
configurations, files, etc. Data from this source control can then further be divided into
different branches for teams to work on. Source control tools give you these features to
exploit. A few examples of source control tools are Git, Subversion, and SVN.

Issue Tracking-
 P a g e | 19

An increase in transparency results in clearer vision, making it easier and faster to

track issues. There are issue tracking tools, but there is a condition: all the teams
should be using the same tracking tool. A few examples of these issue tracking tools
are Jira, ZenDesk, and Backlog.

Configuration Management-

Wouldn’t it be perfect if all your system was automatically configured and updated
without you having to worry about it? Configuration management tools are meant for
that. These tools help manage your infrastructure as code, which then avoids
configuration drifts across environments. A few examples of configuration
management tools are Ansible, Puppet, and Chef

.Continuous Integration-

A good software development cycle gets the code developed in chunks by different
teams and then continuously integrates them. The codes might work perfectly fine
individually but can create issues when integrated. Continuous integration tools let you
detect errors quickly and resolve them faster. A few examples of continuous integration
tools are Bamboo, Jenkins, and TeamCity.

Binary Repositories-

A product might be getting developed on a daily basis or an hourly basis. The code
needs to be flowing smoothly from the developer’s machine to the production
environment, thus a repository manager is a good way to bridge this gap. Repositories
contain collections of binary software artifacts, metadata, and code. A few examples of
binary repositories are Artifactory, Nexus, and Maven.

Monitoring-

As the name suggests, monitoring is a must in DevOps for smooth execution.

Monitoring tools ensure service uptime and optimal performance. A couple of
examples of monitoring tools are BigPanda and Sensu.

Automated Testing-

The entire integrated code needs to be tested before passing it to the build. The quicker
the feedback loop runs, the quicker you reach your goal. A few examples of automated
testing tools are Telerik, QTP, and TestComplete.
 P a g e | 20

Development-

Another great concept of DevOps that allows the application deployment to be

frequent and reliable is development. Deployment tools let you release your products
faster to the market. A few examples of development tools are the Docker toolset, and
IBM uDeploy.

Database-

Finally, there’s handling the data. Data is valuable for getting insights, and every
application development requires a lot of data. Database management tools help you
handle cumbersome data with ease. Some examples of database management tools are
RazorSQL, TeamDesk, etc.

Above are some of tools that has been used in different phases.

7.Benefits of DevOps

Here are some benefits of DevOps-

1. Stabilize the Workplace

Are you aware that the stress brought on by the introduction of new features, repairs,
or upgrades has the potential to undermine the stability of your entire work
architecture and be totally counter-productive? Stabilization is a key benefit of devops.

With the tighter DevOps feedback loop, enhance your working environment with a
balanced and steady approach to operation. Working collaboratively and quickly are
key components of DevOps.The success of a company can be significantly impacted
by changes to QA automation, staging server accessibility, the allocation of
responsibilities between ops and Devs.
 P a g e | 21

With quick turnarounds and enhanced processes, it also increases the likelihood of
market rivalry.The software development life sequence gains discipline and efficiency
thanks to a set of work culture norms and ideas introduced by a DevOps pipeline.

2. Achieve Quicker Deployment

Delivering features and updates more quickly and frequently can not only please
consumers but also enable your business to stand out in a crowded industry.

Unquestionably, a major benefit of the DevOps approach is the chance to create new
systems more effectively by incorporating feedback from engineers, team members,
and important stakeholders. Businesses may stay afloat by using the DevOps strategy,
which leads to implementation that is consistent and uniform.

These methods allow IT businesses to deploy more quickly than slower performers.

3. Outstanding Product Quality

Another benefit from DevOps is the considerable improvement in the product’s

quality results from frequent user input gathering, collaboration between the operation
and development teams, and other factors.

Automated testing in DevOps streamlines, accelerates, and improves the testing

process from integration through staging.

Automation supports excellent product testing by identifying problems early and

decreasing the likelihood that a defect will enter production.

This ultimately lowers the price tag associated with new product introductions.

4. Dependable Issue Resolution

One of the main benefits of DevOps implementation is that it ensures a swift and
reliable response to technical issues in software management. Optimizing the most
crucial business operations is more of a benefit of DevOps.

Teams learn to move faster—release small changes more frequently

 P a g e | 22

Identify problems in almost real-time, and react by moving forward—by swapping the
error-prone traditional waterfall process for a continuous pipeline from growth to
operations. An organization can relentlessly improve with the aid of DevOps.

5. Enables Organisation Flexibility

It’s no secret that becoming more agile in your business operations can help you
maintain a competitive edge. DevOps has made it possible to get the scale needed to
overhaul the company.

Development teams must now, more than ever, dismantle their departmental barriers
and work together and with one another in a constantly changing environment.By
fostering the crucial environment of shared cooperation, coordination, and alignment
via globally dispersed IT teams, DevOps paves the road for enhancing business agility.
The previous role-based boundaries are muddled in such a supportive DevOps
environment. The consistency and timeliness of deliverables are the joint responsibility
of the two team members.

6. Automation fosters Creativity

DevOps has greater advantages than the traditional paradigm since it makes it simpler
to discover and quickly fix problems. The team has more time to frame novel ideas as
the defects are automated and tested repeatedly.By empowering teams to comprehend
customers’ expectations and learn more, DevOps fosters innovation. Creative thinking
often results from combining various viewpoints and exchanging ideas.

DevOps promotes and cultivates an environment where developers are not

constrained by a set of rigid guidelines. This implies that as long as the desired
outcomes are achieved, any project’s scope is always open to innovation.

7. Constant Software Delivery

In the DevOps philosophy, it is up to all departments to keep things stable and

provide new features. Software is delivered uninterruptedly and swiftly as an outcome,
unlike the traditional procedure.Everyone in a company that has adopted DevOps is in
charge of creating an application that performs as intended. The entire team shares the
 P a g e | 23

same goals in terms of marketing time, stability, security, user experience, quality, and
performance. DevOps makes sure everything is in order; every change is documented,
and everyone is aware of how each release will affect quality. Adopting the DevOps
mindset not only makes software delivery quicker, but it also improves quality and
stability.

8. Lowers Production Costs

By bringing both new updates and maintenance under one larger tent, DevOps assists
in reducing the production and administration costs of your departments with good
coordination. The truth is, this is a popular and widely known benefit of devops.

DevOps teams can avoid long-lasting problems by placing a significant emphasis on

performance across the whole lifecycle. This makes it easier to prevent needless and
expensive rework. Competitive advantage and improved profitability result from
this.Multidisciplinary knowledge is a strength of DevOps experts. Because it balances
the workflow across the operations team, this boosts productivity.

Automation and productivity can support keeping DevOps teams lean. Additionally,
automation does away with the necessity for specialists. Without having to pay
premiums, organizations can cross-train generalists across specialties. Effective
procedures even stop expensive time wasters while lowering dangers

9. Transparency Enables Max Output

In the traditional IT industry, a lot of time is wasted waiting on manual work, or by

being forced to repeatedly solve the same issues. Being busy productively is way
different from being tied with unproductive tasks, and the churning of time results in
discontent and sadness.

With DevOps, the team members may easily communicate with one another, thanks to
the process’ promotion of collaboration and the elimination of silo(ing). The latter
helps them become more concentrated in their area of expertise. DevOps practices
have thus been incorporated, which has also increased employee efficiency and
productivity.
 P a g e | 24

DevOps IT operations models make deployments predictable and relieve workers from
tedious, repetitive duties so they can work on more worthwhile projects.

10. Reduces Error

When the processes of development and operations are carried out simultaneously,
identification errors occur quickly.Without moving forward, mistakes can be fixed to
avoid catastrophic failures. The short development cycle encourages regular code
releases. Application code, configuration, and infrastructure issues can be identified
earlier and rectified right away.

It’s the feedback loop in DevOps that helps improve software development quality.
They also ensure that the development, testing, and deployment results are delivered
on time.

8.How does DevOps compare to traditional development methods?

DevOps has evolved over several years to become the go-to methodology for
developers. It’s been adopted by some of the worlds most successful companies –
Netflix, NASA, Etsy and Hertz. The rise in DevOps has been thanks to more
companies adopting an agile development process. And technology is evolving to keep
up with this trend too – look at Microsoft for example, they’ve created Azure DevOps
which comes packed with industry-leading features such as Azure Pipelines, Azure
Boards, Azure Repos and much more. If you’re looking to find out exactly what
DevOps is, how it compares to traditional methods and how you can adopt it to benefit
from some of these new technologies then you’ve come to the right blog.

How efficient are the development cycles?

 P a g e | 25

 Traditional methods often focus on planning big releases, which are much
riskier due to the amount of work involved. When working in longer cycles
with infrequent releases things can often become complex quite quickly.
You’ll be up against hard deadlines compiled with a list of added features.
Whilst the big releases look impressive, they are often an inefficient way of
working.
 DevOps on the other hand takes a different approach. They run with smaller
releases that are often much easier to understand and test – making the release
a lot less risky. It’s also easier to manage if things don’t go to plan as there
isn’t so much to fix. By running more frequent smaller releases, DevOps
enables your business to quickly respond to any new customer needs or
requirements.

How do they manage scheduling?

 Traditional methods often use planning and scheduling systems, to help

manage any development. Within traditional methods there are typically a lot
of moving parts to a development cycle, making scheduling quite a challenging
task.
 DevOps is built on continuous smaller releases and automation from a
dedicated team, making it much easier to schedule. You’ll be planning for the
coming weeks as opposed to a few months, giving you better visibility of your
team’s time. Plus, by having a dedicated team working on this, you’ll be able to
coordinate everything effectively rather than having to schedule different
people in different roles.

What’s the big deal?

 Traditional methods often make an event of their upcoming release or update. A

lot more work would have gone into a single release when a company uses
traditional methods – meaning there’s a lot more at stake and much higher risk.
Have you ever seen developers locked in a room for hours on end before a big
launch? That’s because they’ve been working weeks, if not months for this
 P a g e | 26

release and are spending the final push fire-fighting any last-minute issues to
hit their hard launch date.
 DevOps works in much smaller, more frequent cycles, meaning they don’t go
popping the confetti every time they launch a release or update. There’s a lot
less risk involved as not as much work would have been required since the last
cycle. Plus, with automated testing in place, they can rest assured knowing that
their environments are in sync. DevOps only promote from one stage to
another if they are confident it will work. Thereby, eliminating the release
window so they can move new functionality into productions at a faster rate.

How easy is it to turn data into actionable improvements?

 Traditional methods will typically have to get numerous different parties

involved when trying to collate information and data, which often ends up in a
wordy report that’s shared with management. Lengthy reports can typically
become a bottleneck as it’s not clear on what data is relevant and can result in
unactioned tasks.
 DevOps enables you to quickly react to data thanks to the automated processes
within the team. Meaning, you won’t have to sit and scroll through pages of
information. By having a dedicated team gathering data from the application,
you’re able to ensure that everyone within that team has a better understanding
of the relevant information and data. This not only eliminates the time taken to
gather the data but also to get sign-off from management.

What type of culture do they encourage?

 Traditional methods are often risk-averse. The culture is built around trying
their absolute best to not harm the business, which results in them having a lot
of pressure to get things perfect. When in reality, is anything ever perfect?
 DevOps creates a culture very different from this. They adopt a ‘fail early’
culture, understanding that failure is inevitable. That’s why they’ve created a
strong structure and process around controlled failure through continuous
testing, smaller deployments and automation. The team adopts the mindset of
the sooner you fail, the smaller the impact and the quicker you recover.
 P a g e | 27

What metrics do they use to measure success?

 Traditional methods use a cost and capacity model which looks at how much
they get done for the least amount of money. The key challenge with this model
is that it can be difficult to cut costs but still maintain the same capacity –
which is why a lot of companies using traditional methods have to regularly
outsource tasks.
 DevOps has taken this model one step further by adding in ‘flow’ since new
applications should be measured by the time involved. This encourages them to
review the end cycles time to identify any areas of waste by calculating true
productivity so they can focus on the activities that add the most valuable.

What do they define as a completed task?

 Traditional methods often complete a task by doing their part and passing it
onto the next person. They’ll be so focused on completing a task by meeting
the deadline rather than making sure what is done is deployable. Using this
method can often lead to a loss in quality and a lack of accountability.
 DevOps on the other hand focuses on creating a cross-functional team where
everyone’s accountable for the task being completed. All team members will be
working towards the same goal and will therefore have the same definition of a
completed task, which is creating high-quality software.

9.Challenges and Solutions with real life examples

Companies using DevOps are undergoing a serious culture shift. But before
understanding the reason behind it, let’s take a look at what is DevOps? DevOps is a
methodology that brings the “Dev” and “Ops” team together. This practice aims in
delivering products at a faster pace by using different automation tools. DevOps helps
businesses that are keen on improving the flexibility and agility of their team. In this
article, we will look at some fast-growing MNCs and startups that have implemented
DevOps.
 P a g e | 28

Fig.9.1 Dev+Ops

The following list of Companies using DevOps have seen triumph:

 Amazon
 HP
 Etsy

9.1. AMAZON

Fig.9.2 Amazon

Problem

 You must be aware that Amazon is one of the biggest e-commerce companies
in the world. But back in 2001, their website followed a traditional monolithic
architecture. Here, all processes were coupled together and run as a single
service
 Over time as the source files grew, it became hard to scale, maintain, and
upgrade their applications on physical servers

Solution

To solve the problems of the monolithic architecture, Amazon moved from physical
servers to cloud-based Amazon Web Services (AWS). Currently, AWS follows
a microservice architecture as shown in the figure below. Within this architecture, the
client initially makes a request. Here a load balancer inspects the client request and
 P a g e | 29

assigns it to the correct microservice. In turn, the microservice has a target group that
keeps track of the instances and ports. In Amazon, they are three types of
microservices namely, Users, Threads, and Posts.

Fig 9.3 AWS

Features and tools

Now that we know how a microservice works, let us look at some of the tools and
features Amazon implement to adopt DevOps practices.

Developers apply frequent but small changes over their code via version control tools
like Git and GitHub. Practices like code deployment help fix bugs and add new
features to improve the underlying software application.

AWS CodeDeploy is one such service that keeps track of deployments and simplifies
the software release process.Amazon also uses Apollo, a simple one-click internal
deployment tool. Apollo’s job is to deploy a specified set of software across a group of
hosts. It also provides versioned artifacts and test rollbacks.

On the other hand, practices like Configuration management and infrastructure-as-

code help to monitor and make changes in the software. It keeps track of the system’s
performance and resources used by developers. This way, the testing team can identify
problems before in hand and fix them immediately.

9.2. HP
 P a g e | 30

Fig.HP

In 2006, HP’s LaserJet Firmware division built different products(printers, scanners,

etc.). This entire project was led by the director of LaserJet Firmware, Gary.

He analyzed developers spent around 5% of their time developing and supporting new
features while the rest went into planning, integration, and testing.

Problem

 Gary’s team consisted of around 400+ developers distributed across countries

like the USA, Brazil, and India but only made two software releases per year!
This is because LaserJet models had separate code bases which developed
enumerable inefficiencies
 Software bugs were detected via manual testing after 6 weeks of writing code.
Fixing a bug that incurred within a code weeks ago, was labor-intensive and
tiresome for the developers
 This is where the team needed a new approach to remove the bottleneck

Solution

The HP team adopted Continuous Integration/Continuous Deployment

(CI/CD) pipeline and test automation.

As you can see in the given figure below, their first step was to create a common
platform to support all the products and models. This was called trunk-based
development or continuous integration which eliminated toil caused by the integration
of different code branches.
 P a g e | 31

Fig.9.5 HP team

They also built a set of automated unit tests running against the trunk, which reduced
the 6 weeks manual test time, thereby improving product quality and inducing faster
feedback.Within these automated tests, HP uses a tool called “Stopped the line” that
alarms the developer when code breaks any of the unit tests or builds.

9.3. ETSY

Fig.9.6 Etsy

Etsy is one of the earliest Companies Using DevOps. It is an American e-commerce

website focused on selling handmade and vintage supplies.

Problem

 Initially, Etsy struggled with the development of their organization because

they adopted the monolithic architecture
 Their deployment rate was about two times a week resulting in the isolation of
departments. Etsy had to find a way out of this traditional system

Solution
 P a g e | 32

The new chief technology officer(CTO) brought in a team to adopt DevOps practices.
As shown in the figure below, the CI/CD pipeline helped in deploying services about
50 to 100 times a day.

The first release of code is to a random set of users within the organization. After
testing and feedback, it is then pushed on to the entire community of Etsy.

Fig.9.7 Chain

Advancements and tools

In code deployment, Etsy uses Deployinator a tool that offers one click-
deployments. It helps deploy code about 40 times a day.

They also use Amazon Web Services(AWS) to perform their DevOps operations.

The entire testing phase can thus be automated with the help of a very famous
Continuous Integration tool called Jenkins. It helps with the smooth functioning of
the CI/CD pipeline. Jenkins now executes more than 14,000 test suites per day.

Etsy developed Kale to detect outliers within data. Kale helps to monitor every
deployment performed to make sure the application is user-friendly and stable.

10.The Future of DevOps: Possibilities and Challenges

DevOps has changed how we think about development and operations and has
made it possible for organizations to release more software in less time. We are at a
 P a g e | 33

point where companies struggle to maintain their competitive edge as they compete
with companies that have adopted DevOps.

The future of DevOps is not without its challenges. Maintaining the balance
between software delivery speed and quality will be tricky. The future of DevOps
needs more focus on automation, monitoring, and security.DevOps teams must have
a shared understanding of their company's business objectives and goals. To ensure
these objectives are met, organizations should coordinate better with their
stakeholders on what needs to be delivered from a technical perspective. The future
of a DevOps role is that of a particularly optimistic one.

The Future of DevOps: Based on Industry

The future of DevOps is changing as the industry changes. In the past, it was all
about automation; now, it's all about artificial intelligence. It's not just about the
technical side; many people are working on applying AI to DevOps, and there are
many use cases already. A DevOps Foundation Certification Training
Course can bring out the importance of DevOps.

1. IT industry

DevOps can streamline operations and make it easier for developers to release new
features. DevOps’ future in the IT industry is a bright one. With the rise in the
popularity of DevOps, it is becoming more critical for companies to hire DevOps
professionals. DevOps professionals are responsible for automating tasks and
overseeing the entire process from development to deployment. They are expected
to understand software development's technical and non-technical aspects deeply.

2. Telecommunication

DevOps is a software development method that uses software engineering and

operations engineering practices. It is about collaborating with people in different
disciplines to create high-quality, stable, and secure products.

3. Healthcare
 P a g e | 34

DevOps uses practices that help bridge the gap between development and
operations. It is not uncommon for companies to use DevOps for their software-
based products, but one can also use it in other industries, such as healthcare.

4. Hospitality

The hospitality industry is one of the most rapidly evolving industries in the world.
With the help of technology, it has become easier for hotels to provide better service
to their guests and make their lives more convenient. Some hotels even use
Artificial Intelligence (AI) to help them with tasks like room service, saving time
and money.

5. Banking

DevOps is based on the idea that if you can get faster feedback loops and more
frequent deployments, you can release software more often and improve your
product. Banking and finance companies increasingly rely on DevOps for their IT
infrastructure because they must comply with strict regulations such as PCI DSS
(Payment Card Industry Data Security Standard).

6. Insurance

In the insurance industry, DevOps has been used for many years as a way to
automate processes that are time-consuming or difficult for humans to do. It
includes everything from claims processing to underwriting.

7. Manufacturing

The future of DevOps is based on industry. Manufacturing is a critical industry that

can benefit from implementing DevOps practices. DevOps has been around for a
while and has been successful in the manufacturing industry.

8. Inventory management

DevOps has evolved from a niche set of tools into an enterprise-wide practice that
spans a variety of business functions and activities, including product development,
 P a g e | 35

marketing, sales, and customer service. Other areas include IT operations

management (ITOM), quality assurance (QA), security engineering (SENG), project
management (PM), and human resources (HR). Therefore, it suffices to say that
the future of DevOps jobs is beaming with opportunities.

10.1 The Future of DevOps: Based on Location

Many companies have widely adopted DevOps worldwide due to its ability to
increase the speed of delivery of software and services. DevOps demand in the
future is rising with the upcoming times. The future for DevOps is here to show its
popularity.

1. India

India boasts a high population of over 1 billion people. This country has some of the
best tech talents in the world, which is why it's becoming a popular destination for
outsourcing and offshoring jobs. India has seen an increase in DevOps-related jobs,
and startups are using DevOps to help them scale their business quickly and
efficiently. India's large population and high concentration of tech talent will make
it an attractive destination for DevOps to prosper.

2. United States

In the future, DevOps will be location-agnostic and will be an essential part of the
global economy. The United States has a significant advantage in this area because
it has a large population of skilled engineers and developers.

3. Canada

Canada has several DevOps conferences, meetups, and groups. One example is the
Canadian Developer's Conference (CDNConf), an annual conference that brings
together developers from all over Canada to learn about new technologies and
network with like-minded individuals. In addition to CDNConf, several meetups and
groups have popped up in recent years, such as DevOps Vancouver
or TorontoDevOps.
 P a g e | 36

4. United Kingdom

In the UK, the future of DevOps is promising because there has been increased
adoption of DevOps in the last few years. The government has made it easier for
businesses to adopt DevOps by making changes in legislation that will remove
barriers to embracing it.

5. Australia

Australia is a compelling case for DevOps as most of the country is in a single time
zone, with fewer natural disasters. Any outage or downtime will not affect a large
part of the population. In Australia, many organizations have embraced DevOps to
improve the quality and speed of software delivery. For example, Australian
telecommunications company Telstra has been using DevOps to develop new
applications for its customers since 2010.

6. Singapore

Singapore has been identified as a country that has the potential to become the next
Silicon Valley. With its strategic location, Singapore can attract talent from all over
the world. Singapore's government is also investing in new technologies and
supporting startups so they can grow and innovate. With this, it will be easier for
companies to find talent in Singapore and ensure that their DevOps teams are
equipped with the latest technologies.

7. Dubai

Dubai is a city that has been rapidly developing in recent years. It is home to some
of the most cutting-edge innovations in the world, such as the hyperloop, artificial
intelligence, and autonomous vehicles.

Future of DevOps Jobs

DevOps is the union of software developers and operations who work together to
ensure that the developed, released, and maintained software is more stable,
 P a g e | 37

efficient, and secure. The future of DevOps jobs looks bright as there are a lot of job
opportunities in this field.

Many new companies are looking for talented professionals to fill these positions.
DevOps has become a vital part of today's organizations as it ensures continuous
delivery of high-quality code faster with improved security and stability.

10.2The Future of DevOps: What it Will Look Like in 2030

DevOps is an emerging technology that has rapidly changed our work. As the world
becomes increasingly digital, the pressure on companies to innovate faster than ever
is increasing.

DevOps is a system that helps organizations work more efficiently together to meet
these demands. According to Allied Market Research, the DevOps global market is
projected to reach a 24.2% hike in 2020.

Statista claims that 21% of software development professionals will strategize the
DevOps approach in 2022. The future of DevOps is, thus, substantially bright. The
future of DevOps jobs is also significantly more promising compared to other
technology areas.

Conclusion
 P a g e | 38

Although not all of these ideas are novel, the word “DevOps” refers to a movement
quickly gaining favor in the technical community. DevOps strives to enhance
communication between developers and operations personnel to produce higher-
quality, more dependable, and quicker software. DevOps has the potential to
revolutionize how IT is managed and delivered. The ability for teams at all levels of a
company to work together on development projects makes it easier for them to reach
their goals faster and with less friction. This allows organizations to release more often
while reducing costs by eliminating unnecessary downtime during new software
releases.

To make the journey to the cloud smooth, efficient, and effective, technology
companies should embrace DevOps principles and practices. These principles are
embedded in AWS, and form the cornerstone of numerous AWS services, especially
those in the deployment and monitoring offerings.The DevOps approach is based on
deep involvement of both the operational and development teams during all steps of
product creation. It may take some effort to integrate DevOps in your process, but
eventually it will help you to create an agile and scalable system that’s ready for rapid
change and growth.

References
 P a g e | 39

All collected data and information related to this topic have been collected from these
sites-

Sr No. Links

1. https://en.wikipedia.org/wiki/DevOps

2. https://www.collegelib.com/devops

3. https://aws.amazon.com/devops/what-is-devops

4. https://cloud.google.com/devops

5. https://www.collegelib.com/t-devops-a-software-development-method-
seminar-abstract-report.html

6. https://learn.microsoft.com/en-us/devops/what-is-devops