Windows Azure - tutorial.wmlcloud.com

Change page: < 1 2 3 4 > | Displaying page 2 of 4, items 51 to 100 of 199.

Working with Data in the Surveys Application : Displaying Data (part 3) - Displaying Questions & Displaying the Summary Statistics

The application stores the definition of a survey and its questions in table storage. To render the questions in a page in the browser, the application uses the MVC EditorExtensions class.

Working with Data in the Surveys Application : Displaying Data (part 2) - Session Data Storage

The Surveys application must maintain some state data for each user as they design a survey. This section describes the design and implementation of user state management in the Surveys application.

Working with Data in the Surveys Application : Displaying Data (part 1) - Paging through Survey Results

The owner of a survey must be able to browse through the survey results, displaying a single survey response at a time. This feature is in addition to being able to view summary statistical data, or being able to analyze the results using SQL Azur

Microsoft Azure: Enterprise Application Development - Queue Storage

A single Azure account can have any number of queues. Each queue is composed of messages, each of which carries the data or processing instructions that need to be acted upon by the back-end servers

Microsoft : Azure Enterprise Application Development : Web Role

In Azure, a web role is an HTTP or HTTPS endpoint, and so a web role can include both front-end websites as well as web services. Web roles can also make outbound connections to web services via HTTP.

Microsoft Azure: Enterprise Application Development - Worker Roles

Building worker roles is fairly simple they are just class libraries that inherit from the Microsoft.ServiceHosting.ServiceRuntime.RoleEntryPoint class. Worker roles are automatically started when their host instance is started

Working with Data in the Surveys Application : Saving Survey Response Data

When a user completes a survey, the application must save the user’s answers to the survey questions to storage where the survey creator can access and analyze the results.

Working with Data in the Surveys Application : Testing and Windows Azure Storage

From the perspective of Windows Azure, any test that depends on Windows Azure storage requires complex setup and tear-down logic to make sure that the correct data is available for the test to run

Working with Data in the Surveys Application : A Data Model for a Multi-Tenant Application

The application collects most of the subscriber data during the on-boarding process. The Logo property contains the URL for the subscriber’s logo. The application stores logo images in a public BLOB container named logos.

Enterprise Application Development : Azure Monitoring and Diagnostics

As diagnostic data are logged, the data are buffered in memory. In order for us to retain the data for analysis, we need to make sure that the data persists in a proper storage container.

Enterprise Application Development : Azure Diagnostics under the hood & Enabling diagnostic logging

When we create an Azure application using one of the default templates, collection of Windows Azure, IIS, and Windows Diagnostic logs is enabled by default. We can see the setup in the template files.

Building a Scalable, Multi-Tenant Application for Windows Azure : Scaling the Surveys Application

Survey owners must be able to view some basic summary statistics that the application calculates for each survey, such as the total number of responses received, histograms of the multiple-choice results, and aggregations such as averages of the range results.

Building a Scalable, Multi-Tenant Application for Windows Azure : Scaling Applications by Using Worker Roles

You can use worker roles in Windows Azure to offload resource-hungry operations from the web roles that handle user interaction.

Building a Scalable, Multi-Tenant Application for Windows Azure : On-Boarding for Trials and New Customers

When you’re rending an object with WireFrame enabled, you see only the triangles rendered, but not the pixels inside of them. For the next option, turn on the ScissorTestEnable (the default is false)

Introduction to SQL Azure : Creating our database

The portal database design is very simple, consisting of only five tables. The Jupiter ERP database has only three tables, and will be a local database (this will not live in SQL Azure; it is a representation of an on-site ERP system)

Introduction to SQL Azure : Migrating schema and data

For an on-premise SQL Server, to move a database, we'd commonly use a backup and restore, or detach and reattach neither of those options are available to us in SQL Azure.

Introduction to SQL Azure

If we reach the maximum size limit set for a Web Edition database (5 GB), then it is not easy to migrate from a Web Edition database to a Business Edition database.

Overview of SQL Azure

SQL Azure can be used individually or in conjunction with other Azure services. In either case, local applications can connect directly to SQL Azure. When used in conjunction with Windows Azure services, local applications can also access data stored in SQL Azure via web services.

Microsoft Azure : Designing our Sample Application

All RV sales are handled by independent dealers, who work with our customers and place the customers' orders directly into our ERP system using remote terminals

Microsoft Azure : Setting Up for Development

In order to build an Azure application, we need a framework to access the underlying classes, a development environment, and possibly a few hotfixes as well. The downloads necessary vary by OS (32 or 64 bit, XP or 7), language choice (.NET or PHP), and development environment (Visual Studio or Eclipse)

SOA with .NET and Windows Azure : Service Performance Optimization Techniques

Tuning service runtime performance will improve the utilization of individual services as well as the performance of service compositions that aggregate these services.

Service-Oriented Presentation Layers with .NET : A Simple Service-Oriented User Interface

To create a new module, we need to add a new Silverlight class library project to the solution, set the project’s name to FirstModule, and add references in the module to the following Composite Application Library assemblies

Service-Oriented Presentation Layers with .NET : Design Patterns for Presentation Logic

Prism uses proven design patterns to increase developer productivity and to promote an architecture that supports modularity and “evolvability,” the use of shared services and the minimization of cross-team dependencies.

Service-Oriented Presentation Layers with .NET : Windows Presentation Foundation and the Prism Library

Windows Presentation Foundation (WPF) was introduced with the .NET framework 3.0 and is comprised of a series of classes and tools that leverage modern advances in graphics and UI technology in support of establishing a framework for highly composable presentation layer design.

Working with Windows Azure Platform AppFabric Service Bus (part 2) - Defining a REST-Based Service Bus Contract & Creating the Service Bus Message Buffer

Message buffers are small, temporary caches of messages that can be held for a short time before they are retrieved. They are particularly useful in Web programming model scenarios when AppFabric Service Bus bindings are not available.

Working with Windows Azure Platform AppFabric Service Bus (part 1) - Setting up the AppFabric Service Bus

The Service Bus was optimized for .NET developers using WCF, both in terms of performance and usability. A central component of the Service Bus is the scalable, available, and load balanced messaging fabric relay service that supports a variety of messaging mediums, including SOAP (versions 1.1 and 1.2), REST, and various WS-* standards.

Windows Azure Platform AppFabric Service Bus : Service Bus Connectivity Models

The Service Bus is designed to support REST interactions between services and consumers and provides several REST-based APIs for establishing and managing the configurations and relationships implemented in the Service Bus.

Windows Azure Platform AppFabric Service Bus : Introducing the Service Bus

As the name suggests, the Service Bus establishes a platform-agnostic messaging infrastructure. It essentially provides a foundation of connectivity fabric that supports a variety of inter-service messaging frameworks and patterns.

SOA with .NET and Windows Azure : Orchestration Patterns with BizTalk Server - State Repository & Compensating Service Transaction

Microsoft’s BizTalk Server manages orchestration state in much the same way as WF, except that state management is not extensible or configurable.

SOA with .NET and Windows Azure : Orchestration Patterns with BizTalk Server - Process Centralization

The BizTalk Server product is bundled with a visual orchestration designer tool that can be used to model business process logic as executable orchestrations.

Orchestration Patterns with BizTalk Server : Example

A project team with Superior Stamping has chosen to expose the Order Fulfillment orchestration as an ASMX Web service. The orchestration receives three different message types grouped into the OrderFulfillmentPort

Orchestration Patterns with BizTalk Server : Process Abstraction and Orchestrated Task Services

The encapsulation of BizTalk-defined orchestrations within orchestrated task services is straight forward when compared to WF. BizTalk orchestrations can be constructed for either synchronous or asynchronous invocation

SOA with .NET and Windows Azure : WCF Extensions - WCF Management Tools

Deployed services need to be tuned for performance, managed, and administered in order to meet SLA requirements. Service custodians are typically responsible for managing services through these post-implementation lifecycles.

SOA with .NET and Windows Azure : WCF Extensions - WCF Extensibility

The WCF platform provides built-in support for a range of distributed communication protocols, including transport and message encoding protocols using channel bindings.

SOA with .NET and Windows Azure : WCF Extensions - WCF Discovery

WS-Discovery is a multicast protocol used to discover services within a network. It provides a standardized means of discovering services at runtime by allowing services to locate other services using UDP multicast messages or via a discovery proxy.

Service-Orientation with .NET : Entity Abstraction with a .NET REST Service

Over the course of several years Standard Mold has collected various types of customer-related data. They started out with a simple data model, but different departments added data based on other pre-defined and ad-hoc models, some of which were specific to departmental systems.

Service-Orientation with .NET : Utility Abstraction with a .NET Web Service

Standard Mold is interested in creating a Notification service. They have a number of different systems that already notify people about IT system failures and outages, but this legacy architecture requires that their SMS sending software support four different SMS vendors, and has therefore become complex and expensive to maintain

Service-Orientation with .NET : Service Reusability and the Separation of Concerns

The SOA design patterns catalog establishes a set of foundational service patterns responsible for identifying and defining the scope of functional service contexts and boundaries, as well as service capabilities.

Service-Orientation with .NET : Service Discoverability

Service Discoverability is not just about documenting the service, its capabilities, and messages, it is about ensuring that whatever documentation is produced has a high level of communications quality.

Service-Orientation with .NET : Exception Shielding

Services are sometimes designed to return detailed data about the nature of a given exception, thereby inadvertently disclosing information about their underlying architecture that can be abused by malicious consumer programs.

Service-Orientation with .NET : Service Abstraction & Validation Abstraction

Regardless of whether you are building services as Web services or REST services, you can define message schemas with data types and validation logic that establish specific constraints and a specific level of validation granularity.

Service-Orientation with .NET : Service Loose Coupling and Service Capability Granularity

Each service capability encapsulates an independent set of functionality. Sometimes this functionality will impose specific requirements that pre-determine the capability’s granularity.

Service-Orientation with .NET : Service Façade

When pursuing logic-to-contract coupling, additional coupling flexibility can be built into the service architecture by further establishing layers of implementation logic.

Service-Orientation with .NET : Decoupled Contract

Ultimately, the combination of logic-to-contract and consumer-to-contract is considered to establish the healthiest foundation for achieving balanced loose coupling within and between services

Service-Orientation with .NET : Service Loose Coupling

The goal of the Service Loose Coupling principle is to allow services to develop and evolve with minimal impact on each other, a consideration that is key to achieving the Increased Organizational Agility goal of service-oriented computing.

Service-Orientation with .NET : Service Contracts and Interoperability - Canonical Protocol

In heterogeneous environments it is common for systems to have difficulties communicating directly. Some may be using the TCP as a transport protocol, while others may only be capable of using HTTP over TCP, or even SOAP (over HTTP and TCP)

Service-Orientation with .NET : Service Contracts and Interoperability - Data Model Transformation

One goal of the Standardized Service Contract principle is to avoid having to transform data at runtime. This means that the more successfully and broadly we are able to apply this principle, the less need we will have for patterns like Data Model Transformation

Service-Orientation with .NET : Service Contracts and Interoperability - Canonical Schema

The XML Schema Definition Language is a highly successful industry standard that has received broad cross-platform support within, and well beyond, the SOA industry.

Service-Orientation with .NET : Standardized Service Contract

There are various ways of going about contract-first development with .NET. The primary consideration is in determining in what sequence to define the various parts of a service contract.

Cloud Services with Windows Azure : Windows Azure Storage

Windows Azure Storage supplies a managed API and a REST API, both of which essentially provide the same level of functionality. The managed API is provided through the Microsoft.WindowsAzure.StorageClient namespace