7. Why
On and Off
비사용
Compute
특정기간에만 리소스를 사용하는 작업
(예, 배치작업) 해당 작업을 위한 시스템 투자의 어려움 기간
Average Usage
Cloud? Growing Fast
Compute
빠른 성장에 따른 시스템 리소스의 대응능력
서비스 사용이 급격하게 증가하게 되는 경우
하드웨어가 이에 대응하기가 어려움 Average Usage
컴퓨팅 Unpredictable Bursting
Compute
예상하지 못한 시스템의 사용 또는 게획되지
않은 시스템 자원의 증가 및 감소
패턴
Average Usage
Predictable Bursting
Compute
예상가능한 시스템 사용의 증감
(예, 명절기간 쇼핑몰)
10. 클라우드 서비스
패키지 Infrastructure Platform Software
소프트웨어 (as a Service) (as a Service) (as a Service)
관리/개발
응용 프로그램 응용 프로그램 응용 프로그램 응용 프로그램
데이터 데이터 데이터 데이터
관리/개발
런타임 런타임 런타임 런타임
미들웨어 미들웨어 미들웨어 미들웨어
관리/개발 대상
서
비
O/S O/S O/S O/S 스
서 제
비 공
가상화 가상화 가상화 스 가상화
제
서버 서버 서 서버 공 서버
비
스
저장소 저장소 제 저장소 저장소
공
네트워킹 네트워킹 네트워킹 네트워킹
19. Windows Azure Cloud
Web Role
A Instance DB
A- Worker
A Instance Role
A Instance
B- Worker
Role
B Instance
B Instance C- Worker
Role
C Instance
20.
21.
22.
23.
24. • Table 저장소는 키값을
이용한 noSQL 저장소
구현
• 저비용으로
비정형화된 데이터를
응용 프로그램에서
사용하기 위한
고성능의 저장소 개념
25.
26.
27.
28.
29.
30.
31. •
사용자의 위치와 가까운 서비스와 연결하여 •
프로그램의 성능 개선
자동화된 Fail-Over를 통하여 응용 프로그램의
가용성을 증가
Editor's Notes
안녕하세요? 마이크로소프트의 이건복입니다.오늘 제가 설명드릴 내용은 Windows Azure에 대한 내용입니다. (클라우드 컴퓨팅)
클라우드 컴퓨팅에 대해서 간단히 알아 보고 Azure에 대해서 설명을 드리도록 하겠습니다.
청중에게 질문:클라우드가 무엇이라고 생각하십니까?‘클라우드’라는 이름은 인터넷을 구름모양의 아이콘으로 표시했던 것으로 유래가 되었다고 합니다. (wiki)
소유의 개념제레미 리프킨(Age of Access)의 이야기물리적 지배력의 증명에서 배타적의 사용권의 개념토지, 자동차의 소유에서 Access로브리태니커의 사례 (사전->광고)아리스토텔레스
Slide Objectives:Explain how Microsoft thinks of the cloudSpeaking Points:There are numerous terms and definitions floating around in the industry for “the cloud”, “cloud computing”, “cloud services”, etc.Microsoft thinks of the cloud as simply an approach to computing that enables applications to be delivered at scale for a variety of workloads and client devices.The cloud can help deliver IT as a standardized service…freeing you up to focus on your business
조금 더 쉽게 IT소유의 개념이 인터넷에서도 동일하게 Access의 개념으로 전환이것은 선택의 문제가 아닌 필수적인 고려요소
낭비되는 리소스와 불필요한 리소스의 차이점을 설명
Speaking Points:There is a lot of talk in the industry about different terms like Platform as a Service, Infrastructure as a Service, and Software as a Service.Since PDC08 when we first announced the Windows Azure our focus has been on delivering a platform as a service offering where you can build applications. Where the platform abstracts you from the complexities of building and running applications. We fundamentally believe that the future path forward for development is by providing a platform. In fact, as you’ll see in a few minutes, we believe that there are a number of new capabilities that should be delivered as services to the platform.Notes:There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS. ----Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaking Points:With this in mind, it’s important to understand how to talk about our Cloud Services offerings.There is a lot of confusion in the industry when it comes to the cloud. It’s important that you understand both what is happening in the industry and how we think about the cloud. This is the most commonly used taxonomy for differentiating between types of cloud services.The industry has defined three categories of services:IaaS – a set of infrastructure level capabilities such as an operating system, network connectivity, etc. that are delivered as pay for use services and can be used to host applications. PaaS – higher level sets of functionality that are delivered as consumable services for developers who are building applications. PaaS is about abstracting developers from the underlying infrastructure to enable applications to quickly be composed. SaaS – applications that are delivered using a service delivery model where organizations can simply consume and use the application. Typically an organization would pay for the use of the application or the application could be monetized through ad revenue. It is important to note that these 3 types of services may exist independently of one another or combined with one another. SaaS offerings needn’t be developed upon PaaS offerings although solutions built on PaaS offerings are often delivered as SaaS. PaaS offerings also needn’t expose IaaS and there’s more to PaaS than just running platforms on IaaS.
Slide Objectives:Explain the differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaking Points:Here’s another way to look at the cloud services taxonomy and how this taxonomy maps to the components in an IT infrastructure. Packaged SoftwareWith packaged software a customer would be responsible for managing the entire stack – ranging from the network connectivity to the applications. IaaSWith Infrastructure as a Service, the lower levels of the stack are managed by a vendor. Some of these components can be provided by traditional hosters – in fact most of them have moved to having a virtualized offering. Very few actually provide an OSThe customer is still responsible for managing the OS through the Applications. For the developer, an obvious benefit with IaaS is that it frees the developer from many concerns when provisioning physical or virtual machines. This was one of the earliest and primary use cases for Amazon Web Services Elastic Cloud Compute (EC2). Developers were able to readily provision virtual machines (AMIs) on EC2, develop and test solutions and, often, run the results ‘in production’. The only requirement was a credit card to pay for the services.PaaSWith Platform as a Service, everything from the network connectivity through the runtime is provided and managed by the platform vendor. The Windows Azure best fits in this category today. In fact because we don’t provide access to the underlying virtualization or operating system today, we’re often referred to as not providing IaaS.PaaS offerings further reduce the developer burden by additionally supporting the platform runtime and related application services. With PaaS, the developer can, almost immediately, begin creating the business logic for an application. Potentially, the increases in productivity are considerable and, because the hardware and operational aspects of the cloud platform are also managed by the cloud platform provider, applications can quickly be taken from an idea to reality very quickly.SaaSFinally, with SaaS, a vendor provides the application and abstracts you from all of the underlying components.
오늘 제가 몇몇 가지 내용을 말씀 드렸고 드릴 예정이지만가장 중요한 내용이 바로 이 슬라이드에 있습니다.전체적인 Azure서비스의 내용에 대한 모델입니다.
사용자의 위치와 가까운 서비스와 연결하여 프로그램의 성능 개선자동화된 Fail-Over를 통하여 응용 프로그램의 가용성을 증가
