Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Desvendando a Plataforma de Serviços Windows Azure
Similaire à Desvendando a Plataforma de Serviços Windows Azure (20)
Dernier
Dernier (6)
Desvendando a Plataforma de Serviços Windows Azure
- 1. Desvendando aPlataforma de Serviços Azure Lucas A. Romão laromao@oxygenhost.com.br http://laromao.spaces.live.com
- 6. SQL Azure
- 8. Demo
- 13. Custos de capitais antecipados para a infra-estrutura
- 14. Aluguéis de máquinas, conectividade e software
- 15. Menor Controle
- 19. Pagamento de capacidade fixa, mesmo se ocioso
- 20. Infra-estrutura compartilhada de diversos clientes
- 24. Serviços de alto nível
- 25. Pay as you goOn-Premises Servers Hosted Servers Cloud Platform
- 27. Simplificar a implantação de aplicativos & gestão
- 28. Flexibilidade de aplicativos e infra-estrutura
- 29. Custoeficiente com picos de aumento de carga
- 31. Plataforma de Serviços Azure Compute: Ambiente virtualizado baseando no Windows Server Storage: Armazenamento durável, escalável e disponível Management: Gerenciamento automatizado, orientada ao modelo do serviço Database: Processamentorelacionalpara dados estruturados/não Estruturados. Service Bus: General purpose application bus Access Control: Controle de acesso controlado por regras, baseada em declarações’
- 32. A Plataforma Windows Azure Experiência do Desenvolvedor Use as ferramentas e skills Third party cloud Web applications Web and clouds Use as ferramentas e skills existentes. Compute Storage Management Management Relational data Connectivity Access control On-premises Composite applications LOB Applications
- 34. Windows Azure é um local onderodamos nossasaplicações.
- 35. Windows Azure é umaplataformacloudcomputing, sendo assim, ele foi projetado para escalar.
- 36. Internamente existem muitos servidores.
- 37. com VMs rodando Windows.
- 39. e aqui é onde sua app roda. SuaAplicação
- 40. O gerenciamento de tarefassãoautomatizadospeloFabric Controller.
- 41. Vocêdizao Fabric Controller o quequerfazer, e ele descobre como fazê-lo.
- 42. Service Scaling Your Service Service Service DNS Service Service Service Service Service LB Service Web Portal (API) LB Model Fabric Controller
- 43. Your Service Service DNS Service Service Service LB Web Portal (API) ! LB Model Service Monitoring & Recovery Fabric Controller
- 45. Tables
- 47. Data Mining ETL Reporting Data Sync Reference Data SQL Data Service Data Warehouse Database: Processamentopara dados estruturados e nãoestruturados Data Sync: Sincronização para clientes conectados ocasionalmente Reporting: Auto-serviço de criação e compartilhamento de relatório Data Mining: Análise & dados auto-atendimento de tendências ETL: Data transformation & cleansing across on/off premise Reference Data: Ampla variedade de conjuntos de dados de referência
- 50. ServiceBus AccessControl Service Bus: General purpose application bus Access Control: Rules-driven, claims-based access control
- 51. Hello Azure Services : Composing Azure Services ASP.NET Web Site SQL Azure (SOAP) http://data.database.windows.net (REST) .AppFabric Service Bus http://servicebus.windows.net/... http://...cloudapps.net (Running in Windows Azure) AppFabric Control Service Manufacturer Service (Running on-premises)
- 52. Service Bus On-PremiseBusiness Apps PartnerApplications Service Bus Community & Internet Services
- 53. Contratação Windows Azure é Umaplataformacomputacionalutilitária, vocêpagaporaquiloquevocêutiliza.
- 55. 1 GB = $9.99 / month
- 56. 10 GB = $99.99 / month
- 57. Bandwidth = $0.10 in / $0.15 out / GBWindows Azure Two or more role instances 99.95% Compute = $0.12 / hr Storage = $0.15 / GB stored / month Tx = $0.01 / 10K Bandwidth = $0.10 in / $0.15 out / GB AppFabric 99.9% Messages = $0.15 / 100K Bandwidth = $0.10 in / $0.15 out / GB
- 58. DEMO
- 77. Dicas para estudo http://channel9.msdn.com/learn/courses/Azure/ Azure Academy - Aprenda na prática http://msdn.microsoft.com/pt-br/azure/default.aspx http://azureservicesbr.ning.com/
- 78. Próximos Eventos Presenciais FATEC Tatuí – 20/05 Hortolândia – 01/06 Webcasts Windows Azure – Storage (Blobs, Tables e Queues) SQL Azure AppFabric Silverlight + Azure BPOS
- 79. DÚVIDAS ??? @LucasRomao laromao@oxygenhost.com.br http://azureservicesbr.ning.com @AzureServicesBR http://laromao.spaces.live.com
Notes de l'éditeur
- Slide objectives: Explain what the cloud is in relationship to on-premises servers and hosted severs. Speaking Points: To put the cloud in perspective, let’s first think about the available options for deploying and running your application today. Today, there are a few established approaches for deploying and running applications.ServerOn one side you have on-premises servers or a self-hosted model. With on-premises servers, you bring your own machines, connectivity, software, and in some cases software licenses.You have complete control of the environment, the software stack, the hardware, etc.However, you also have complete responsibility. Your organization must have the skills and expertise to operate and manage the environment and software. You must take on the responsibility of patching the environment, replacing hardware, etc.These days, very few people want to be in this business. However, on-premises servers are not going away anytime soon. In some cases organizations have to maintain solutions running in an on-premises environment due to regulatory, data, or privacy requirements.Hosted ServersAn established alternative to the on-premises model is with a hosted environment.With hosted servers, you are effectively renting capacity – including machines, connectivity, and in some cases software.With this model, you have less control then when you’re managing your own servers. For instance, you can’t walk up to a machine, and plug in an external drive to load data. Or easily make hardware or software adjustments to optimize for performance. However, you also have fewer responsibilities when it comes to operating, updating, patching, and managing the environment. What is generally much more attractive about a hosted model is the cost model.The upfront capital costs can be much lower then building out your own infrastructure. However, one of the downsides is that you generally pay for the fixed capacity on a monthly basis – even if your application is idle. CloudWhat we are starting to see in the industry is the emergency of the cloud as a platform for building and running applications. So what is the cloud and how does it relate to these established options for running your apps?A cloud platform is designed as a shared, multi-tenant infrastructure.Cloud platforms utilize virtualization to: share hardware resources, provide isolation of applications or tenants, and also to provide a more dynamic infrastructure.Ability to scale out your application over multiple server instances.Because it is a shared infrastructure, there is even less control compared to a hosted environment. As this is an emerging space, there is a wide range of different types of cloud solutions. Some of the solutions focus purely on providing virtualized infrastructure. Servers you can remote into. However, many cloud platforms are starting to focus on raising the level of abstraction – so you can focus on building and deploying applications rather than remoting into machines and maintaining or patching servers. Old:Level of abstraction varies greatly today with the solutions in the marketWithin the cloud, there are things that are delivered as an infrastructureServices – services provided by the infrastructure and services you would consume programmaticallyFinally, one of the primary reasons why organizations ranging from startups, independent software vendors, and large enterprises are starting to investigate the cloud is the pricing model. With a cloud platform, you can expect a pay as you go pricing model – where you pay for what you use. [build arrow] I believe it’s important to understand that the cloud is part of a continuum. It is one of potential approaches that you can begin to use to deploy and run your applications. However, it’s important to understand that the cloud is not the silver bullet. It is not the perfect solution for every application. Notes:We view cloud as scale out, automated service management, high availability and multi-tenantBut cloud has other considerations: location, infrastructure, business model, ownership and management
- Slide objectives:Define SQL Services and enumerate the current and future services.Speaking Points: Question: How many of you use SQL Server today?Imagine having SQL Server functionality ranging from SQL Server databases, to reporting, analytics, and integration services and having that functionality available to you in the cloud – without having to deploy and configure clusters and manage and operate a SQL environment.That is what we want to accomplish with SQL Services. We are extending the SQL Server Data Platform to the cloud.This will happen over several releases of the Azure Services Platform. In the short term, we are focusing on two key services. SQL Data Services and Data Sync.SQL Data ServicesAt the Mix conference in 2008 we first announced SQL Data Services. SQL Data Services is designed to provide data storage and query capability in the cloud. Today with SQL Data Services, we are exposing data through SOAP and REST based programming models and we are just starting to surface the underlying database capabilities such as joins. Over time we will continue to provide more relational support that is familiar to developers using SQL Server.Data SyncWe are also supporting data synchronization, so you can easily synchronize data to or from the cloud using the Sync framework. If you’re not familiar with the sync framework, it is an extension to the .NET Framework 3.5 that provides an extensible engine for synchronization across a variety of data sources.Future servicesThe grey boxes that you see here represent future services or capabilities that will be added to SQL Services in future versions of SQL Services. For example, one of the common areas of feedback we have heard from partners and customers is the desire to perform data transformations and processing in the cloud. We have also heard requests for reporting and analysis services in the cloud – much like SQL Server developers are familiar with today.Notes: Databases are crucial to business applications, and really crucial to all applications that are being built today. And so what we're doing is we've taken and built a scale-out implementation of SQL Server that we're making available through something we call SQL Services. SQL Services is built on SQL Server. It's SQL Server underneath it. And over time, what we will do is provide more and more of the capabilities that you're familiar with in on-premises SQL Server into the SQL Services.And so today we have a SQL data services environment that lets you build a database built on entities. Over time, we'll grow those capabilities in the relational space. We will, in the future, be providing capabilities like data synchronization to allow you to synchronize on-premises information as well as information on mobile workers with the cloud services to be able to synchronize that data, data mining services and analysis services to be able to dig in and understand what's happening at a detailed level, things eventually like geospatial and a whole broad set of things we'll be bringing available to this environment. The basic goal here is that with the cloud environment, you need a database just like you needed one on premises, and in fact, we're providing that set of scale-out services as a part of the Azure Services Platform.
- Slide objectives: Define and enumerate the Windows Azure Platform Appfabric (aka .NET Services.)Speaking points: Much in the same way that SQL Services is about extending SQL Server to the cloud, we are also extending key .NET capabilities to the cloud as services.We call these .NET Services. Some of you maybe familiar with previous codenames such as BizTalk Services.These services are really key components you would need for building distributed, connected applications. When we talk about connecting to your existing on-premises applications and enabling the composition of hybrid (Cloud + on-premises) applications – that is where .NET Services really comes in.There are currently two .NET Services: the Service Bus & the Access Control ServiceService Bus:The Service Bus is designed to provide a general purpose application bus, available on the internet at internet scale. You can really thin of the Service Bus as being similar to an Enterprise Service Bus that many enterprise organizations have today. However, we believe that when providing a Service Bus as a programmable service on the internet, there are a wider range of scenarios for many more types of organizations.Fundamentally, the .NET Service Bus is about connecting applications across network and application boundaries and making key message exchange patterns such as publish and subscribe messaging very simple.Access Control:The Access Control service is designed to provide rules-driven, claims-based access control for applications. Essentially, this allows you to define authorization rules for your applications using the claims-based approach that we are adopting within many Microsoft products and technologies and that is becoming adopted in the industry.Notes: Windows Azure has the .NET Framework built into it so that you can use those services within your application.But just like your application must be designed to scale out, the services that we have built into Windows over time in .NET also need to be designed and built in a way that can scale out naturally. We want to create services for you, and that's the purpose of .NET services, creating a pool of resources available to you to take advantage of and do things within your application very simply. So we're including a built-in, scale-out implementation of a service bus. The service bus lets you connect your on-premises systems securely into the cloud, into the Azure environment, while allowing your data and your information to traverse firewalls, solving a problem that is a bane of many application developments.
- Slide objectives: Explain how the demo scenario composed services from the Microsoft Services Platform. Speaking points: So we’ve seen a lot of services, let’s spend a couple minutes reviewing the architecture of our Hello Azure Services example. First, we have an ASP.NET Web site. That web site is running in Windows AzureNotes: