शैडोइंग अभ्यास: I Wish Someone Explained DevOps to Me Like This - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

हर मोड पूरी स्क्रीन का अभ्यास कक्ष खोलता है।

185 वाक्य

यदि वाक्य बहुत छोटे या लंबे हों, तो समायोजित करने के लिए Edit पर क्लिक करें।

Imagine an IT company has been hired to build a loan management system for a bank.

It will record loan details, track approvals, and manage repayment information.

The developers are ready to write code, but there is no environment to run it in, no connection to the bank's existing systems,

and no clear way to release or monitor it once it is live.

Where should the team begin, and how do all the parts fit together?

That's what DevOps is for.

For years, developers focused on building features, while operations teams focused on keeping production stable.

Agile helped teams deliver smaller changes, and continuous integration helped developers combine their work more often.

But teams still needed to cooperate when software was released and supported.

The DevOps movement gathered momentum in 2009.

That year, John Alspaugh and Paul Hammond spoke about cooperation between development and operations at Flickr,

and Patrick Dubois helped organize the first DevOps Days event in Ghent.

The name caught on, but the idea was bigger than a job title or a toolset.

People who build and run software need to work together throughout the life of the software.

DevOps is now a popular role in technology.

In this video, we'll explore its ecosystem in 10 sections, from infrastructure and networking, to security, containers, and releases.

We'll follow James, a DevOps engineer hired by the IT company.

His job is to help the developers, security specialists, and bank operations team build, release, and run the loan management system reliably.

The first question is where the system will run.

The bank and IT company need to decide whether to use the bank's own data center, a cloud provider such as AWS,

Azure, or Google Cloud, or a combination.

Their choice depends on the bank's existing systems, security rules, costs, and where its data is allowed to live.

At the beginning, the project has no servers, cloud accounts, access rules, or test environments.

Cloud, platform, or DevOps engineers often work with the bank's infrastructure and security teams to prepare the foundation.

This is commonly called a landing zone.

Think of it as preparing a new building before the project moves in.

It can include cloud accounts or subscriptions, basic network design, access rules, central logging and security controls.

For the loan project, the team might have separate accounts or subscriptions for development, testing and production.

This helps keep the environments organized and limits the effect of a mistake in one area.

The bank may already have a landing zone, in which case James' team works within it and adds only the parts the project needs.

James uses Infrastructure as Code, or IAC, to describe the resources the project needs.

With Terraform, for example, he can write instructions for creating a test environment, its network, and its servers.

The team reviews those instructions and then applies them to create the environment.

If it needs another test environment later, it can use the same instructions instead of rebuilding everything by hand.

AWS CloudFormation and Azure Bicep are other tools for defining cloud infrastructure.

The landing zone gives the project a safe place to run, but it still needs connections to the bank's existing systems.

That brings James to the next area, networking.

Networking connects the loan management system to the people and systems that need to use it.

You can think of it as the roads and gates between different parts of the bank's technology.

The network must provide the necessary routes while controlling which systems and people are allowed through.

The loan system might need to connect to the bank's identity service, database, and existing financial systems.

Developers may need a controlled way to reach a test environment, but that does not mean the environment should be open to everyone on the Internet.

A network includes subnets, which divide it into smaller areas, firewalls, which allow or block connections,

and DNS, which helps systems find each other by name.

A load balancer directs incoming requests to available servers, much like a traffic controller sending cars toward open lanes.

A private connection, or VPN, can provide a controlled route between the IT company's environment and the bank's network.

Cloud providers offer network services, such as AWS VPC and Azure Virtual Network.

Teams might also use NGINX or HAProxy to route traffic.

James works with the bank's network team to make sure the loan system can reach the services

it needs without opening unnecessary paths into the bank's network.

With the environment and its connections planned, the team needs a shared way to record how the software and its setup change over time.

That's what we're going to see next.

source control, and configuration.

Developers use Git to keep a history of their code.

It works like a shared history book.

The team can see what changed, who changed it, and when.

Platforms such as GitHub, GitLab, and Bitbucket give the team a place to store Git repositories and review proposed changes.

For example, when a developer changes how the system calculates a repayment, another team member can review the change before it is added to the project.

If a problem appears later, the team has a record it can use to investigate.

The system also needs different settings in different environments.

The development version might connect to a test database, while the production version connects to the bank's live database.

These settings are called configuration.

James helps the team keep them separate from the application code so that the right settings are used in the right place.

Tools such as Ansible can also apply consistent settings to servers.

The team can keep infrastructure definitions and pipeline instructions in Git too.

That way, it can review a proposed change to an environment just as it reviews a proposed change to the application.

The team can see what is changing before it is applied.

Now the team can track its code and configuration changes.

But how can it quickly tell whether a new change works or whether it has broken something else?

That brings us to continuous integration and testing.

Continuous Integration, or CI, means bringing changes together frequently and checking them automatically.

James sets up a pipeline, a sequence of automated steps, that runs when a developer submits a change.

It might build the application, check its formatting, and run tests.

Jenkins, GitHub Actions, GitLab CI, and Azure Pipelines are common tools for running this kind of pipeline.

Different tests check different parts of the system.

A unit test checks a small piece of code, such as a repayment calculation.

An integration test checks whether parts work together, such as the application connecting to its database.

A broader test can check a complete process, such as recording a repayment and updating a loan record.

The team can also run performance tests to see how the system behaves when it has a lot of work to do.

For instance, can it process the bank's expected number of repayment records during the overnight window?

If a test finds a problem, the team can fix it before the change moves further.

The pipeline gives the team regular feedback instead of saving all testing for the end of the project.

When a change passes its checks, the team needs a reliable way to store exactly what it built.

That brings us to package and artifact management.

Most applications use software components created by other teams.

A Java project might use libraries for connecting to a database, while a JavaScript project might use packages for its interface.

A package manager downloads those components and keeps track of their versions.

Maven and Gradle are common in Java projects, while NPM is common in JavaScript projects.

When the loan system is built, the result is a package, also called an artifact, that the team can test and release.

Tools such as JFrog Artifactory and Sonatype Nexus store artifacts so the team can retrieve them later.

They also help track which versions of outside libraries went into the build.

James encourages the team to build the release package once, test it, and then move that same package through the environments.

If they build one package for testing and a different one for production,

it becomes harder to know whether the bank is getting the version that was actually tested.

The team can now identify and store the software it built.

The next question is how to make sure that software runs consistently on different computers and environments.

That leads us to containers and orchestration.

A container packages an application in a form that can run consistently in different environments.

Docker is a popular tool for building containers.

100

Think of a container as a labeled box carrying the application and the pieces it needs to run.

101

James' team can use a container for the loan system in development, test it, and then use the same container image when preparing a release.

102

This helps reduce differences between the project's test environment and the bank's production environment.

103

If there are many containers running across many machines, the team may need a system to manage them.

104

Kubernetes can schedule containers, restart them if they fail, and coordinate updates.

105

It can also be configured to add or remove capacity as demand changes.

106

Docker helps package containers.

107

Kubernetes helps manage them across a group of machines.

108

The bank project might use Kubernetes if its needs and approved platform call for it, or it might use a simpler managed service or virtual machines.

109

Whatever platform the team chooses, it still needs to protect the application and the information it handles.

110

That brings us to security.

111

The loan system handles important bank information, so the team needs to control who can access it and protect the information it uses.

112

Security is part of building and running the system, not just a check added before launch.

113

The team gives each person and service only the access it needs.

114

A developer might need access to a test environment, for example, without having unrestricted access to production.

115

Passwords, keys, and other secrets should be stored securely, rather than written into the code.

116

HashiCorp Vault and Cloud Secret Management Services can help manage them.

117

James also adds security checks to the pipeline.

118

Code scanning looks for common mistakes in the project's own code.

119

Dependency scanning checks whether the outside libraries the project uses have known security problems.

120

Container scanning checks the packaged application for vulnerable components.

121

These tools cannot guarantee perfect security, but they can help the team find and fix many issues earlier.

122

The team works with the bank's security specialists to decide

123

which checks are needed and what should happen if a check finds a problem.

124

They also agree how to protect information as it moves between systems and how to avoid exposing sensitive details and logs.

125

Building security into the development and release process is often called DevSecOps.

126

Once the team has built and checked a secure package, it needs to decide how that package will move into the bank's environment.

127

Now we come to releases and deployments.

128

A release is a version of the software the team intends to make available.

129

A deployment is the process of putting that version into an environment where it can run.

130

Continuous delivery means keeping software ready for release through an agreed process.

131

Continuous deployment goes further by automatically releasing changes that pass the required checks.

132

The bank may require a person to approve each production release, but the pipeline can still build the software,

133

run checks, and prepare the release for that approval.

134

The important part is that the steps are clear and repeatable.

135

Teams can also introduce a new version gradually.

136

With a canary release, the new version handles a small amount of work first.

137

If it behaves as expected, the team sends more work to it.

138

A rolling deployment updates parts of the system one at a time,

139

while a blue -green deployment prepares the new version alongside the old one before switching over.

140

James works with the bank to choose a release method that fits its system and rules.

141

They agree on the required checks, approvals, and release windows.

142

Once the software is deployed, the team needs to know how it behaves, so its attention moves to monitoring and incident response.

143

Monitoring helps the team see whether the running system is healthy and alerts them when something needs attention.

144

James wants to know, for example, if an overnight repayment process is falling behind or taking longer than expected.

145

The team uses metrics to measure things over time, such as how long a process takes.

146

Logs record events that happened, and traces show the path a request took through different parts of the system.

147

Together, these signals help the team understand both that something went wrong and where to investigate.

148

Tools such as Prometheus and Grafana can collect and display metrics.

149

OpenTelemetry can help gather information from applications, while systems such as Elastic or Splunk can help teams search logs.

150

Cloud providers also offer monitoring services.

151

An alert should give the team a reason to act.

152

If the repayment process is falling behind, the right people need to know and have a starting point for investigating.

153

James helps the team write runbooks, practical guides for common issues, and agree who should respond to an incident.

154

Monitoring helps the team notice and investigate a problem.

155

The team also needs a plan for larger failures, such as damaged data or an unavailable environment.

156

That takes us to reliability, recovery, and cost.

157

The bank and IT company agree how quickly the loan system should be restored after a serious failure

158

and how much recent data it can afford to lose.

159

The team backs up important data and practices restoring it.

160

A backup is only useful if the team knows how to use it and has checked that it works.

161

The team also sets a reliability target, such as how reliably an overnight process should complete and checks whether the system is meeting it.

162

If problems happen too often, the team may need to focus on improving reliability before taking on more changes.

163

This kind of focus on dependable services is associated with site reliability engineering, or SRE.

164

Cost needs attention too.

165

Cloud resources can be added when needed, but resources left running unnecessarily can keep increasing the bill.

166

James helps the team review what it is using, plan for busy periods, and remove resources it no longer needs.

167

Paying attention to cloud costs is often called FinOps.

168

As the IT company takes on more projects, James may help create a shared platform with useful starting points,

169

a code repository, test environment, pipeline, and security checks.

170

That saves new teams from repeating the same setup and helps them start with practices the company already understands.

171

Now we can see how the 10 areas connect.

172

Infrastructure gives the system a place to run, and networking connects it to the bank's systems.

173

Source control tracks changes, CI tests them, and package management stores what the team has built.

174

Containers help the software run consistently, security checks help protect it, and release practices move changes into production in a controlled way.

175

Monitoring, recovery, and cost planning help the team operate it over time.

176

Different projects use different tools.

177

One team might use Terraform and Jenkins.

178

Another might use a cloud provider's tools and GitHub Actions.

179

The important thing is to understand what each part is for and choose tools that fit the project.

180

That is the DevOps ecosystem.

181

People, practices, and tools working together to build, release, and operate software.

182

When you look at a DevOps roadmap, ask what problem each area solves and how it connects to the others.

183

Once you understand that, the tools become much easier to learn.

184

If this helped you connect the pieces, consider subscribing.

185

We'll keep exploring the tools and ideas behind modern software, one project at a time.

ऐप डाउनलोड करें

धाराप्रवाह बोलने के लिए ज़रूरी सब कुछ

AI उच्चारण स्कोरहर वाक्य का स्कोर

IPA अभ्यासहर ध्वनि में महारत

शब्दावलीअपना शब्द भंडार बनाएँ

शब्द गेमखेलते हुए सीखें

QR स्कैन करें

Download on theApp Store Get it onGoogle Play

उसी चैनल से

I Bet Nobody Has Ever Explained the Backend Ecosystem Like This Before

Daily ConversationWorking Adults

LangChain in 5 Minutes (Explained Clearly)

Daily ConversationUniversity StudentsWorking Adults

FOR YOU

अनुशंसित वीडियो

78 वाक्य

इस पाठ की शब्दावली और बोलने के सुझाव

यह स्पीकिंग पाठ वीडियो “I Wish Someone Explained DevOps to Me Like This” पर आधारित है। सबसे ज़्यादा दोहराए गए शब्द ये हैं: environment, test, project, release, James। इस वीडियो में शैडोइंग के लिए 185 वाक्य और 2655 शब्द हैं। बोला गया हिस्सा 16:28 लंबा है। वक्ता लगभग 161 शब्द प्रति मिनट की स्वाभाविक गति से बोलता है, जो रोज़मर्रा की बातचीत के करीब है। केवल 81% शब्द अंग्रेज़ी के 3,000 सबसे आम शब्दों में से हैं, इसलिए शब्दावली कठिन है।

इस वीडियो की मुख्य शब्दावली

वीडियो के 15 सीखने लायक शब्द, उच्चारण और अर्थ के साथ:

शब्द	उच्चारण	अर्थ
package संज्ञा	/ˈpæk.ɪd͡ʒ/	पैकेज, पैकेट
cloud संज्ञा	/ˈklaʊ̯d/	मेघ, बादल
container संज्ञा	/kənˈteɪ.nəɹ/	पात्र, डिब्बा
developer संज्ञा	/dɪˈvɛləpɚ/	विकासक
pipeline संज्ञा	/ˈpaɪpˌlaɪn/	पाइपलाइन
infrastructure संज्ञा	/ˈɪnfɹəˌstɹʌkt͡ʃə/	अवसंरचना
monitor संज्ञा	/ˈmɑ.nɪ.tɚ/	पर्यवेक्षक
database संज्ञा	/ˈdeɪtəˌbeɪs/	डेटाबेस
continuous विशेषण	/kənˈtɪn.juː.əs/	निरंतर
server संज्ञा	/ˈsɝvɚ/	सर्वर
log संज्ञा	/lɔɡ/	कुंदा, लट्ठा
investigate क्रिया	/ɪnˈvɛs.tə.ɡeɪt/	शोध करना
integration संज्ञा	/ˌɪn.tɪˈɡɹeɪ.ʃən/	एकीकरण
instruction संज्ञा	/ɪnˈstɹʌkʃən/	उपदेश, शिक्षण
overnight क्रिया विशेषण	/əʊvə(ɹ)ˈnaɪt/	रात भर

इस वीडियो का व्याकरण

वक्ता जिन संरचनाओं का सबसे अधिक प्रयोग करता है, वीडियो के असली शब्दों के साथ:

संरचना	वीडियो में
Passive voice be + past participle — ज़ोर इस पर कि क्या होता है, न कि कौन करता है	has been hired · was released · is allowed
Present perfect have/has + past participle — बीता हुआ काम जिसका असर अभी भी है	has been hired · has broken · have known

ध्यान देने योग्य उच्चारण

वक्ता 4 बार संक्षिप्त रूपों का प्रयोग करता है, जैसे we'll, we're। इन्हें वैसे ही छोटा बोलें जैसा आप सुनते हैं।

“sh” और “zh” की ध्वनियाँ: integration /ˌɪn.tɪˈɡɹeɪ.ʃən/, instruction /ɪnˈstɹʌkʃən/, configuration /kənˌfɪɡ.əˈɹeɪ̯.ʃən/, specialist /ˈspɛʃəlɪst/, subscription /səbˈskɹɪpʃən/
लंबे शब्द — बलाघात सही रखें: developer /dɪˈvɛləpɚ/, infrastructure /ˈɪnfɹəˌstɹʌkt͡ʃə/, continuous /kənˈtɪn.juː.əs/, investigate /ɪnˈvɛs.tə.ɡeɪt/, integration /ˌɪn.tɪˈɡɹeɪ.ʃən/

हिंदी भाषियों के लिए मुश्किल ध्वनियाँ:

/v/ और /w/ का फ़र्क़ — /v/ में ऊपर के दाँत निचले होंठ को छूते हैं, /w/ में होंठ गोल होते हैं: developer /dɪˈvɛləpɚ/, server /ˈsɝvɚ/, investigate /ɪnˈvɛs.tə.ɡeɪt/, overnight /əʊvə(ɹ)ˈnaɪt/, provider /pɹəˈvaɪ.də(ɹ)/
/z/ — इसे “ज” (/dʒ/) न बनाएँ: expose /ɪkˈspoʊz/, organize /ˈɔɹɡənaɪz/, lanes /leɪnz/, repository /ɹɪˈpɒz.ɪ.t(ə.)ɹɪ/
शब्द की शुरुआत में s + व्यंजन — पहले “इ” न जोड़ें: scan /skæn/, specialist /ˈspɛʃəlɪst/, stable /ˈsteɪ.bəl/

इस वीडियो से अभ्यास कैसे करें

पहले बिना बोले पूरा वीडियो एक बार सुनें और जो शब्द नहीं आते उन्हें लिख लें।
0.75× गति से शुरू करें, एक-एक वाक्य की शैडोइंग करें, और सहज लगने पर सामान्य गति पर लौटें।
अपनी आवाज़ रिकॉर्ड करें और मूल से तुलना करें, ख़ासकर package, cloud, container जैसे शब्दों पर ध्यान दें।

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: I Wish Someone Explained DevOps to Me Like This - वीडियो के साथ अंग्रेजी बोलना सीखें

अभ्यास मोड चुनें

ऐप डाउनलोड करें

I Bet Nobody Has Ever Explained the Backend Ecosystem Like This Before

LangChain in 5 Minutes (Explained Clearly)

How I deploy serverless containers for free

What is Event Driven Architecture (EDA)?

"Customer Obsession" Leadership Principle Explained by Amazon CEO Andy Jassy

Parallel Pump Operation

Helpdesk to Sysadmin - 3 Things You Must Learn First

900+ hours of Learning AI Agents in 9 Minutes

The Digital Transformation of Banking and Financial Services in a New Era

How to design a Deployment Pipeline (GitOps)

Trust the Process: How to Design Teams That Actually Work

What is a PLC and how does it work?

Armchair Architects: Resiliency in the Cloud – Core Patterns

Claude Code Mods Explained: Customize Your Setup