Desenvolvendo software como serviço para negócios
•
1 recomendación•557 vistas
O documento descreve os princípios e benefícios da computação em nuvem, incluindo acesso à internet, recursos compartilhados, autoatendimento sob demanda, elasticidade rápida e pagamento conforme o uso. Ele também discute como as aplicações na nuvem podem trazer economia, foco no negócio, inovação, segurança e outros benefícios.
Recomendados
Recomendados
Más contenido relacionado
Similar a Desenvolvendo software como serviço para negócios
Similar a Desenvolvendo software como serviço para negócios (20)
Desenvolvendo software como serviço para negócios
- 4. • Acesso por Internet • Compartilhamento de recursos • Auto-serviço sob demanda • Elasticidade rápida • Pagamento conforme o uso
- 5. APLICAÇÕES SERVIÇOS COMPUTAÇÃO ARMAZENAMENTO USO COMPARTILHADO E SOB DEMANDA
- 6. Padrões de uso da computação em nuvem
- 10. Plataforma de nuvem pública da Microsoft windowsazure.com
- 11. Plataforma em nuvem de nível empresarial
- 13. Server Rack 1 Server Rack 2
- 27. Serviços de aplicação na nuvem fornecem software através da Internet, sem a necessidade de instalar e executar o aplicativo em computadores próprios.
- 28. • Poupa tempo • Economiza dinheiro • Aumenta o foco no negócio • Inova mais rapidamente • Traz segurança • Melhora o fluxo de caixa • Traz benefícios fiscais • Cria uma comunidade
- 29. • Modelo de negócio • Necessidade grande de marketing • Foco em cliente e serviço • Feedback mais rápido • Uma única versão • Suporte mais eficaz • Qualidade é fundamental • Segurança é pré-requisito
- 31. • Eficiência • Escalabilidade • Elasticidade • Disponibilidade • Tolerância a falhas • Usabilidade • Conectividade • Segurança
- 32. específico Inquilino 1 Inquilino 2 Inquilino 3 Inquilino 1 Inquilino 2 Inquilino 3 configurável Instância 1 Instância 2 Instância 3 Instância Instância Instância Inquilino 1 Inquilino 2 Inquilino 3 Inquilino 1 Inquilino 2 Inquilino 3 eficiente escalável Balanceador de Carga Instância Instância Instância Instância
- 34. Para migrar com sucesso para a modalidade SaaS os ISVs tradicionais têm que mudar fundamentalmente o seu modo de desenvolver, vender e entregar suas soluções de software.
- 35. Uma aplicação que não foi projetada para escalar não vai escalar só porque está “na nuvem”.
- 36. • Multi-tenant • Rich clients • Scale out • Load balancing • Sharding • Asynchronous operations • Federation • Message queues • Stateless services • Publish/subscribe
- 37. Design Data & Content Security Processes Management
- 38. Presentation • ASP.NET C#, PHP, Java • Distributed in-memory cache Services • .NET C#, Java, native code • Distributed in-memory cache • Asynchronous processes • Distributed parallel processes • Transient file storage Connectivity • Message queues • Service orchestrations • Identity federation ACCESS WORK SERVICE BUS • Claims-based access control CONTROL FLOWS • External services connectivity Storage • Relational & transactional data • Federated databases • Unstructured, de-normalized data • Logical partitioning • Persistent file & blob storage • Encrypted storage
- 41. Otimizada para tirar proveito dos pontos fortes das plataforma Azure, .NET e HTML5.
- 43. Aplicativo Cliente Serviços de Negócio SQL Azure Blob Storage
- 44. Cliente Servidor HTML OData CSS WCF Data Services JavaScript Entity Framework JSON SQL Azure
- 45. PCs e Laptops Servidores Smartphones e tablets download Arquivos download estáticos Aplicativo Aplicativo Cliente Cliente Serviços de dados aplicativo dados
- 46. Browser Smartphone Tablet Serviços de Serviços de Serviço de Armazenamento Aplicativo Aplicativo Fila de Mensagens Banco de Dados Federado Processamento Processamento SQL SQL SQL de Mensagens de Mensagens
Notas del editor
- Slide Objectives:Explain the three established terms in the industry for cloud servicesSpeaker Notes: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 differences and relationship between IaaS, PaaS, and SaaS in more detail.Speaker Notes: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.
- Transition:Let’s spend a few minutes talking about what happens when we deploy a cloud service in Windows Azure.
- Speaker Notes:One of the other things we do with Windows Azure to enable that is provide a bunch of Application Building BlocksThese are managed services that we run that provide a lot of value so you can avoid standing up the infrastructure for common capabilitiesYou always can stand up VMs and put anything you want in itBut in a lot of cases you will find that we have built in services that we deliver or that are delivered by our partnersWhat’s cool is that you can use any of these services with a VM, with a Web Site, or with a Cloud Service – so you have flexibility in how you will consume them.
- Speaker Notes:Let’s walk through some of the building block services that we’re providing and in particular highlight some of the new features of these services. If you’ve been using Windows Azure you maybe familiar with some of these services. However, there are several new features we’re enabling with all of them. The first one I’m going to talk about is the SQL DatabaseSQL Database is a service we’ve had for a while as part of Windows AzureIt provides a relational SQL Server database engine in the cloudWe run the SQL engine for you, we do all of the clustering and availability work for you, so you don’t have to worry about standing up your own clustered environment. It’s a fully managed serviceWe also apply security patches and monitor the systemEarlier this month we also released the SQL Reporting support, so you can do reporting and business intelligence on top of the data you store in the SQL database
- Slide Objectives:Understand how SQL Federation extends the scalability model to the database tierTransition:Database elasticity also aligns with all of the other Windows Azure principles around scalability and elasticity, applying them to the server side of things so that you don’t need to worry about them. Speaking Points:With SQL Federation, we’re extending the scalability model to the database tier. Scale your data tier on demand without any downtime, and without any applications changes.Notes:Extending the model of the front tier and the middle tier of the application scale out model. Canonical 3-Tier application scales by adding and removing node. You stand up a few servers on the front tier, a few servers in the middle tier, then the database, then you open up the doors. Users start pouring in, and as user load goes up, you add more servers. However, what do you do with the database? You have to buy a bigger machine. They idea with Federations is to extend the multi-node scalability model into the database, making the database elastic.
- Speaker Notes:We have a great storage system.We talked about this earlier as part of virtual machines for mounting drives. You can think of blob storage as a highly available, scalable, and secure file system in the cloud. You can store any type of data you want in it. You can optionally expose storage through some HTTP URLs and make it public or you can make it private. Similar to databases, you can stand up a new storage account in a few minutes. Continuous geo-replication is enabled by default for storage accounts.
- Speaker Notes:We now have a new distributed cache feature in Windows AzureIt is a low latency, in-memory cache that you can stand up as part of our application It’s elastic so you can dynamically grow or shrink the cache at will, based on how your application is doingYou don’t have to modify any application code or redeploy your application to increase or decrease the cache size. Instead just go into the portal say you want more roles and Windows Azure will automatically spin them upIt also has high availability support. So you can indicate when you cache something that you want to pin the data on at least two cache servers, so if there is a hardware failure you will not loose any data.The Distributed Cache can be used from any language. It now supports the Memcach’D protocol, so if you have apps that use Memcached today you can simply point them to the new distributed cache and they will work with no code changes required.
- Speaker Notes:You can integrate with anyone using Active DirectoryOnce you integrateYou can also take advantage of our new graph API
- Speaker Notes:We also have a bunch of new service bus capabilitiesThe Service Bus is a managed service that provides secure messaging and relay capabilities.It’s great for integrating cloud based solutions with on-premise environments in a very secure way and it enables a very loosely coupled architectureWith the new Windows Azure SDK and Tools for Visual Studio, you can now view information about the service bus directly from within Visual Studio. We are also now introducing cross platform libraries so you can use service bus from any OS whether it’s a VM, web site, or Cloud Service and with any of the languages we support.