Cloud apps with REST APIs using Windows Azure, Asp.NET, ServiceStack and Angu...mobiweave
In this talk, Ash DCosta will show you how to create compelling HTML5 cloud applications, using ServiceStack, AngularJS, Visual Studio and Azure. Creating great REST APIs with ServiceStack is easy, and so is consuming them with AngularJS, and deploying them to the cloud with Windows Azure. Ash will demonstrate all these pieces working together on a small "to-do" web app.
The speaker
Ash DCosta is the founder and chief architect at Mobi Weave, a cloud and mobile solution provider. He has 20+ years of experience in software with Intel, i2 Technologies, IdentityMine, i3Connect and Wells Fargo. You can follow him on Twitter as @softwareweaver.
La plateforme Microsoft Experiences repose sur un système en backoffice bâti sur les derniers produits et services Microsoft.
Dans cette session, vous découvrirez au travers d’un cas concret en production, les nouveautés et les bénéfices apportés par ASP.NET Core 1.0, les bonnes pratiques ainsi que les pièges à éviter pour le faire fonctionner de manière optimale dans Azure.
Seront également abordés les différentes possibilités offertes par ASP.NET et Azure pour rendre votre plateforme extensible en ouvrant de manière sécurisée l’accès à vos APIs.
Cloud apps with REST APIs using Windows Azure, Asp.NET, ServiceStack and Angu...mobiweave
In this talk, Ash DCosta will show you how to create compelling HTML5 cloud applications, using ServiceStack, AngularJS, Visual Studio and Azure. Creating great REST APIs with ServiceStack is easy, and so is consuming them with AngularJS, and deploying them to the cloud with Windows Azure. Ash will demonstrate all these pieces working together on a small "to-do" web app.
The speaker
Ash DCosta is the founder and chief architect at Mobi Weave, a cloud and mobile solution provider. He has 20+ years of experience in software with Intel, i2 Technologies, IdentityMine, i3Connect and Wells Fargo. You can follow him on Twitter as @softwareweaver.
La plateforme Microsoft Experiences repose sur un système en backoffice bâti sur les derniers produits et services Microsoft.
Dans cette session, vous découvrirez au travers d’un cas concret en production, les nouveautés et les bénéfices apportés par ASP.NET Core 1.0, les bonnes pratiques ainsi que les pièges à éviter pour le faire fonctionner de manière optimale dans Azure.
Seront également abordés les différentes possibilités offertes par ASP.NET et Azure pour rendre votre plateforme extensible en ouvrant de manière sécurisée l’accès à vos APIs.
AWS re:Invent 2016: FINRA: Building a Secure Data Science Platform on AWS (BD...Amazon Web Services
Data science is a key discipline in a data-driven organization. Through analytics, data scientists can uncover previously unknown relationships in data to help an organization make better decisions. However, data science is often performed from local machines with limited resources and multiple datasets on a variety of databases. Moving to the cloud can help organizations provide scalable compute and storage resources to data scientists, while freeing them from the burden of setting up and managing infrastructure.
In this session, FINRA, the Financial Industry Regulatory Authority, shares best practices and lessons learned when building a self-service, curated data science platform on AWS. A project that allowed us to remove the technology middleman and empower users to choose the best compute environment for their workloads. Understand the architecture and underlying data infrastructure services to provide a secure, self-service portal to data scientists, learn how we built consensus for tooling from of our data science community, hear about the benefits of increased collaboration among the scientists due to the standardized tools, and learn how you can retain the freedom to experiment with the latest technologies while retaining information security boundaries within a virtual private cloud (VPC).
1. The document describes an end-to-end enterprise architecture solution design from OnePoint4 Re-Sourcing. It includes sections on governance and service management, technical solutions for enterprise data centers, workplace environments, and communications.
2. An integrated service tool suite is used for customer service delivery, including incident, problem and change management. Regional hubs enable centralized governance on a global scale while ensuring local support.
3. Standardized reporting is provided through a multi-layer data warehouse and business intelligence platform, with reports accessible through the MyCustomer web portal.
Microservices are an essential enabler of agility but developing and deploying them is a challenge. In order for microservices to be loosely coupled,each service must have its own datastore. This makes it difficult to maintain data consistency across services.
Deploying microservices is also a complex problem since an application typically consists of 10s or 100s of services, written in a variety of languages and frameworks. In this presentation, you will learn how to solve these problems by using an event-driven architecture to maintain data consistency and by using Docker to simplify deployment.
AWS re:Invent 2016: Workshop: AWS Professional Services Effective Architectin...Amazon Web Services
The AWS Professional Services team will be facilitating an architecture workshop exercise for certified AWS Architects. Class size will be limited to 48. This workshop will be a highly interactive architecture design exercise where the class will be randomly divided into teams and given a business case for which they will need to design an effective AWS solution. Past participants have found the interaction with people from other organizations and the creative brainstorming that occurs across 6 different teams greatly enhances the learning experience. Flipcharts will be provided and students are encouraged to bring their laptops to document their designs. Each team will be expected to present their solution to the class.
Cloud Architecture Tutorial - Why and What (1of 3) Adrian Cockcroft
Introduction to the Netflix Cloud Architecture Tutorial - discusses the why and what of cloud including the thinking behind Netflix choice of AWS, and the product features that Netflix runs in the cloud.
The document summarizes the objectives, process, roles, and activities involved in a Solution Architecture Concept workshop. The workshop is intended to define the scope, components, and architectural overview of a proposed IT solution by bringing together stakeholders to develop a shared understanding of business needs and technical requirements. Key parts of the workshop include preparation activities, a two-day session to discuss business/functional and technology/implementation views, and documentation of findings.
Developing event-driven microservices with event sourcing and CQRS (svcc, sv...Chris Richardson
Modern, cloud-native applications typically use a microservices architecture in conjunction with NoSQL and/or sharded relational databases. However, in order to successfully use this approach you need to solve some distributed data management problems including how to maintain consistency between multiple databases without using 2PC.
In this talk you will learn more about these issues and how to solve them by using an event-driven architecture. We will describe how event sourcing and Command Query Responsibility Segregation (CQRS) are a great way to realize an event-driven architecture. You will learn about a simple yet powerful approach for building, modern, scalable applications.
The document discusses an approach to IT strategy and architecture that aligns business and IT to enable organizations to adapt to constant change. It presents a framework with four views: business, functional, technical, and implementation. The business view defines goals and drivers. The functional view describes how the solution will be used. The technical view specifies how the system will be built. The implementation view details how the solution will be delivered. It advocates for stakeholder participation and using principles, models, and standards across the views.
Structured Approach to Solution ArchitectureAlan McSweeney
The role of solution architecture is to identify answer to a business problem and set of solution options and their components. There will be many potential solutions to a problem with varying degrees of suitability to the underlying business need. Solution options are derived from a combination of Solution Architecture Dimensions/Views which describe characteristics, features, qualities, requirements and Solution Design Factors, Limitations And Boundaries which delineate limitations. Use of structured approach can assist with solution design to create consistency. The TOGAF approach to enterprise architecture can be adapted to perform some of the analysis and design for elements of Solution Architecture Dimensions/Views.
.NET Conf Taiwan 2022 - Tauri -前端人員也能打造小巧快速的 Windows 應用程式升煌 黃
Web 技術要統治世界真的不是說說的,現在到哪裡都可以看得到 web 技術的影子,透過 web 技術打造 Windows 應用程式也早已行之有年,但過去許多工具產出來的應用程式大小都非常龐大,直到 Tauri 的出現提供了我們另外一種選擇,透過 Tauri 我們可以輕易的打造檔案更小、速度更快、也更安全的 Windows 應用程式,而你所要會的,依然還是那些本來就該會的前端開發知識而已!本次分享將帶大家實際看看使用 Tauri 來撰寫 Windows 應用程式是一個怎麼樣的體驗。
Developing Serverless application with Microsoft Azure and Cognitive ServicesJeff Chu
Introduction to Serverless computing, how to develop application with Microsoft Azure Functions and Logic Apps, plus Cognitive Service Text Semantic analysis.
The document discusses Microsoft's .NET conference and platform. It highlights that .NET Core 2.0 has been released and is available for download. It promotes .NET as being able to build any application for any platform and develop with any programming language. It also emphasizes that .NET sees large growth in active developers and popularity. Additionally, it provides statistics on customer success with .NET and shows how .NET powers a variety of applications and services.
Microsoft Azure IoT 手把手實作 @ K.NET by Maduka (2017-8-12)Jeff Chu
A hands-on lab exercise for Microsoft Azure IoT, help students to learn how to use IoT hub, SQL Database, Stream Analytics services to build their IoT solution.
Developing serverless applications with azure functionsJeff Chu
This document discusses developing serverless applications with Azure Functions. Azure Functions allow processing of events using small, isolated pieces of code called functions. Functions can be triggered by events from other Azure services and external sources. Functions are easy to develop, scale automatically, and only charge for the time spent processing events.
The document discusses new features in C# 7.0 including tuples, pattern matching, out variables, and more. It provides code examples demonstrating how to use tuples to return multiple values from functions, type patterns to match types in switch statements, and when conditions to add additional checks to case statements. The examples show enhanced control flow options in C# with these new features.
The document discusses containers and how they compare to virtual machines. It explains that containers provide operating system-level virtualization where the kernel is shared among containers, unlike virtual machines which virtualize hardware. This allows containers to have faster startup and be more resource efficient. The document then provides steps for setting up a container environment on Windows and details how to build, run, distribute, and update container images.
This document discusses Microsoft Azure's support for Linux and Java workloads. It provides an overview of pre-built Linux virtual machine images on Azure including popular distributions like Oracle Linux and Windows Server. It also outlines options for deploying Java applications on Azure infrastructure services, platform services, and using common Java APIs and tools across deployment models. Customer quotes are provided praising Azure's scalability and cost benefits compared to on-premise Linux servers.
35. #GlobalWindowsAzure
MSDN Windows Azure 線上資源
Windows Azure 實作手冊:
http://msdn.microsoft.com/zh-tw/jj590639
Windows Azure 教學影片:
http://msdn.microsoft.com/zh-tw/jj573849
Windows Azure Developer Center:
http://www.windowsazure.com/en-us/documentation/
Slide Objectives:Introduce Azure application ecosystem. Point out that Web Sites, Cloud Service, and Virtual Machines provide a continuous landscape of application development and hosting. Speaking Points:Azure building block services are available across the landscape. Emphasize how Azure can provide robust infrastructure with *global reach* that allows you to reach out to more customers.Notes:This talk usually happens after initial overview of Azure. The assumption is that audience has heard the terms “Web Site”, “Cloud Service”, and “Virtual Machines”. This slide is to put everything into perspective so that the audience can understand the three areas are not isolated offerings.
Slide Objectives:A brief definition of Cloud Service. Speaking Points:Cloud Service defines management, security, deployment, and communication boundary of your services. Notes:This definition emphasize that Cloud Service is a container.
Slide Objective:Understand how a Web Role extends the standard worker roleSpeaker Notes:A web role takes all the capabilities and semantics of a worker role and adds the IIS Hostable Web CoreWeb Roles run ASP.NET websites- they do this by using the IIS hostage web core. pretty much anything that will work in a standard IIS ASP.NET Web Site should work in Windows Azure. At MIX09, we additionally added support for IIS7’s FastCGI capability. As a note, any files that are part of a asp.net project on windows azure are READ ONLY! If you need to be able to change the contents of files:User Blob StorageIf its configuration, use the service model files – which can be changed at runtime.Inbound protocols are http(s) – outbound protocols are any TCP connection but NOT UDP.Notes:http://msdn.microsoft.com/en-us/library/dd179341.aspxhttp://blogs.msdn.com/b/carlosag/archive/2008/04/14/hostyourownwebserverusingiis7.aspxhttp://blogs.iis.net/ksingla/archive/2007/12/20/ins-amp-outs-of-hostable-web-core.aspx
Slide Objective:Understand the 3 common patterns of worker rolesSpeaker Notes:Pattern 1 – Polling Worker role polls a Queue Pops message Performs work Polls queue againPattern 2 Worker listens for inbound TCP requestCan implement with Raw TcpListeners or use WCF or use Hosted Web CorePattern 3 Run a 3rd party processWhen the role starts up or runs use a Process.Start() call to run a standard windows executable E.g. Running a database serverNotes:http://blog.smarx.com/posts/build-your-own-web-role-running-hosted-web-core-in-windows-azurehttp://blog.smarx.com/posts/making-songs-swing-with-windows-azure-python-and-the-echo-nest-api
Slide Objective:Understand the lifecycle of a Windows Azure roleUnderstand the methods that can be overridden in RoleEntryPointUnderstand the events that are raised by role instances when their status is changingSpeaker Notes:Roles will typically extend RoleEntryPointThe fabric calls RoleEntryPoint methods as it starts and stops a roleWaWorkerHost process is started.Worker Role assembly is loaded and surfed for a class that derives from RoleEntryPoint. This class is instantiated. RoleEntryPoint.OnStart() is called. RoleEntryPoint.Run() is called. If the RoleEntryPoint.Run() method exits, the RoleEntryPoint.OnStop() method is called . WaWorkerHost process is stopped. The role will recycle and startup again.As a role changes state it will raise the StatusCheck event.A status of Busy will mean the load balancer will not route requests to the instance.Notes:http://blogs.msdn.com/b/jnak/archive/2010/02/11/windows-azure-roleentrypoint-method-call-order.aspxhttp://msdn.microsoft.com/en-us/library/ee848065.aspx
Slide Objective:Understand the difference between Roles and InstancesSpeaker Notes:The Service model defines the shape of a service- the Roles it will haveendpoints it will listen onTypes of VMs that will be runAt runtime each Role will run at a given scaleSpecifically each role will be deployed onto and executed on one or more VMsA VM runs a single roleNotes:Notes on the various security roles involved in running a Windows Azure accounthttp://blog.toddysm.com/2010/01/subscription-and-service-administration-in-windows-azure.html
Slide Objective:This animation is to reinforce the message in previous slide by showing how roles and mapped to instances during deployment.
Notes:The infrastructure of each Windows Azure data center is notionally divided into multiple sections known as fault domains. These sections of the infrastructure (which are not necessarily individual servers or server racks) are designed in such a way that a failure of one fault domain is extremely unlikely to affect any other fault domain. When you deploy a service, the Windows Azure Fabric Controller automatically locates the roles in at least two different fault domains so that a failure in one domain will not affect all instances of your service.
Slide Objective:Understand what a scale-out application looks likeSpeaking notes:High scale applications often follow this sort of an patternInbound connectivity comes through a load balancerRequests are round robin routedLoad balancer is typically aware of the state of the web servers (i.e. are they up)There are one or more tiers or groups of stateless web or app serversBy stateless we mean that they do not hold state between client requestsStateless means that simple load balancing works – no need for sticky sessionsStateless means that the failure of a web server does not cause major issues for application- it is simply removed from the load balancerA stateful or storage tierThis will generally involve some sort of scale out approach for large appsOften using partitioned databasesOften some sort of queuing mechanismApplications will often perform processing in the background. Improves response time for usersAllows load peaks to be buffered in queuesWindows Azure provides us with a Platform as a Service offering to implement these sorts of applicationsNotes:http://msdn.microsoft.com/en-us/magazine/cc500561.aspx http://msdn.microsoft.com/en-us/library/ff650667.aspx
How to use portal to manage cloud services
Slide ObjectiveCODE – PACKAGE – UPLOAD – DEPLOYShows how service makes it from code living in Visual Studio to a running deployed instance in Windows AzureShow how Roles are packaged up and uploaded with the config to Windows AzureSpeaking PointsCode is compiled, then packaged into a single file. This is the service package.This, along with the configuration/service model – are deployed via the web portal.NotesVisual Studio 2010 with the updated tools now supports automated seamless package/upload/deploy using Service Mngt Api