쉐도잉 연습: Cloud Models - CompTIA Network+ N10-009 - 1.3 - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
When you're deploying a cloud -based application, you also need to consider who will be accessing that application and from where.
2
If you're creating an application that anyone on the internet would need to access,
3
then you would probably want to include it in a public cloud so that everyone can gain access.
4
But if you're building out a cloud -based application that is for internal use only,
5
you may want to deploy this to your own virtualized local data center where you have a private cloud.
6
organizations, we often use both of these.
7
And we need a hybrid configuration of both public and private clouds for all of these applications.
8
One type of cloud model is software as a service, or SAS.
9
This is commonly associated with software that is on demand.
10
You have a login screen in your browser, you log in, and now you have access to the application.
11
Someone else has written the application, someone else manages the application, your data is stored somewhere within that application,
12
and you don't have to do anything else to be able to use that particular app.
13
You don't have a local installation of software, manage or upgrade any of the software itself.
14
Instead, you simply log in and use the app.
15
This allows for centralized management of the application and the data that you're putting into the application,
16
which means everything is being stored on a third party cloud platform.
17
This is a complete application offering, and you don't have to do any type of development work to be able to use that app.
18
A good example of software as a service would be an app like Google Mail or Office 365, where you simply log in and use the app.
19
There may be times when you would like to build your own application and deploy and manage your own data,
20
and all you really need are the computing resources to be able to run that application.
21
In that model, you want to use Infrastructure as a Service, or IAAS.
22
Sometimes you'll see this referred to as Hardware as a Service,
23
or HAAS, because you're effectively using hardware in the cloud and then using your own software on top of that.
24
This means that you would be responsible for installing your software and managing all of the data associated with that software.
25
If the software needs to be upgraded, you would be the one to upgrade it on your infrastructure as a service model.
26
The application that you're using and the data that you're putting into that application is still in the cloud.
27
But you have much more control over the access and security of that data when you're using infrastructure as a service.
28
A good example of infrastructure as a service is with web service providers, where you can buy time on a particular web server,
29
and they make that server available to everyone on the internet.
30
A middle ground between software as a service and infrastructure as a service is Platform as a Service, or PAAS.
31
This is still in the cloud, but you're the one who manages all of the development efforts to customize the application to your specifications.
32
The cloud provider gives you all of the tools necessary to build this particular app.
33
You can think of this as a series of building blocks provided by the Platform as a Service infrastructure,
34
filled out those blocks to create your own application.
35
The underlying engine that runs the application is the responsibility of the Platform as a Service provider.
36
And your responsibility is to build and maintain the apps that are running in Platform as a Service.
37
A good example of a Platform as a Service infrastructure would be something like Salesforce .com,
38
where they give you all of the tools necessary to create a customized application running on the Salesforce .com platform.
39
Here's an example of a cloud responsibility matrix that you might find with any cloud service provider.
40
In this chart, I've separated out software as a service, platform as a service, infrastructure as a service, and then an on -prem device that you would manage yourself.
41
Obviously, with on -prem, everything from the data to the applications to the physical data center are all the responsibility of the customer.
42
But with infrastructure as a service, you have the physical data center, the physical network, physical hosts, all provided by the cloud provider.
43
And then you handle all of the other pieces of that particular application.
44
With Platform as a Service, you can see that network controls,
45
applications, and the identity and directory infrastructure may be shared between the customer and the cloud provider.
46
But you'd still be responsible for the accounts, devices, and the information and data.
47
With Software as a Service, much more of these are provided by the provider themselves.
48
Everything associated with the applications is clearly in the responsibility of the provider.
49
Everything above that would still be the responsibility of the customer.
50
So depending on the type of infrastructure you want, and the type of responsibility that you're willing to take on,
51
you'll need to pick the right cloud model for your application deployment.
📺 같은 채널
✨ 추천 영상
C12
315 문장
Azure App Service and Virtual Network Integration Options
Business EnglishUniversity StudentsWorking Adults
C11
177 문장
Mini Project - Implementing a Simple Web Identity Federation Application
Business EnglishUniversity StudentsWorking Adults
C13
360 문장
Terraform Scenario Based Interview Questions and Answers | DevOps Interview
Business EnglishInterview EnglishUniversity Students
C15
34 문장
Marketing Research Essentials Intro, Models & Intelligence
Business EnglishUniversity StudentsWorking Adults
B21
9 문장
What is a Server? Servers vs Desktops Explained
Business EnglishUniversity StudentsWorking Adults
C11
128 문장
Demystifying MCP | Architect Insights
Business EnglishUniversity StudentsWorking Adults
C13
56 문장
What is SMT (Surface Mount Technology)? PCB Assembly (Part 3)
Business EnglishUniversity StudentsWorking Adults
C12
105 문장
Oracle Integration Cloud(OIC): A Quick Overview
Business EnglishUniversity StudentsWorking Adults
C17
67 문장
8 Most Important System Design Concepts You Should Know
Business EnglishUniversity StudentsWorking Adults
C11
60 문장
Course Preview | SC-100 | Microsoft Cybersecurity Architect
Cambridge Exam PrepBusiness EnglishUniversity Students
C11
309 문장
Claude Code: The Advanced Guide (99% of Devs Skip These Features)
Business EnglishUniversity StudentsWorking Adults
이 수업에 대하여
이번 수업에서는 클라우드 모델에 관한 중요한 개념을 다루며, 다양한 클라우드 서비스의 유형과 각각의 책임 분담에 대해 학습합니다. 학습자는 소프트웨어 서비스(SaaS), 인프라 서비스(IaaS), 플랫폼 서비스(PaaS)의 정의와 특징을 이해하고, 이들 각각이 제공하는 서비스와 그에 따른 관리 책임이 어떻게 다른지를 알게 됩니다. 이를 통해 클라우드 기반 애플리케이션을 개발할 때 고려해야 할 요소들을 익히게 될 것입니다.
주요 어휘 및 구문
- 클라우드 모델: 다양한 클라우드 서비스의 유형을 설명하는 개념.
- 소프트웨어 서비스 (SaaS): 사용자가 소프트웨어를 설치할 필요 없이, 클라우드를 통해 제공받는 서비스.
- 인프라 서비스 (IaaS): 하드웨어 자원을 클라우드에서 제공받아 사용자가 직접 소프트웨어를 관리하는 모델.
- 플랫폼 서비스 (PaaS): 애플리케이션 개발을 위한 플랫폼을 클라우드에서 제공받는 서비스.
- 온프레미스: 사용자가 직접 관리하는 전통적인 데이터 센터.
- 데이터 보안: 클라우드 서비스 사용 시 데이터 접근과 보안 관리의 중요성.
- 개발 도구: 플랫폼 서비스에서 사용자에게 제공되는 애플리케이션 구축 도구.
연습 팁
이번 비디오를 통해 영어 발음과 이해력을 향상시키기 위해 shadowspeak 기술을 활용하는 것이 좋습니다. 비디오에서 다루는 내용을 반복적으로 듣고 따라 말해보세요. 특히, 클라우드 관련 용어는 발음이 다소 어려울 수 있으므로 천천히 발음해보는 것이 중요합니다. 비디오의 속도에 맞추어 shadow speech 연습을 진행하면, 발음 교정과 함께 자연스러운 억양을 익힐 수 있습니다. 유튜브 영어 공부 시간에는 클라우드 모델과 관련된 표현을 암기하는 것도 효과적입니다. 각 서비스의 정의와 특징을 이해한 후에는 청취한 내용을 자신의 말로 요약해보세요. 이 과정을 통해 영어 말하기 능력을 한층 더 높일 수 있습니다.
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.