Monday, October 13, 2008 at 8:00 AM - Friday, October 17, 2008 at 5:00 PM (CT)
Introduction
Designing large-scale distributed systems is hard. New technologies make it easier to comply with today's communications and security standards, but don't auto-magically give you a robust and scalable system. Join Udi for a course packed with the wisdom of companies like SUN, Amazon, and EBay.
Tried-and-true theories and fallacies will be shown, keeping you from making those same costly mistakes today. Communications patterns like publish/subscribe and correlated one-way request/response will be used in conjunction with advanced object-oriented state management practices for long-running workflows. If you enjoy deep architectural discussion, if you are in charge of building a large-scale distributed system, if you want to know more about how the big guys run their systems, this is for you.
About Udi
Udi Dahan is The Software Simplist, recognized by Microsoft Corporation with the coveted Most Valuable Professional award for Solutions Architecture now 4 years running. Udi is a Connected Technologies Advisor working with Microsoft on WCF, WF, and Oslo. He also serves as a member of the Patterns & Practices Advisory Board for the CAB and Prism. He provides clients all over the world with training, mentoring and high-end architecture consulting services, specializing in Service-Oriented, scalable and secure .NET architecture design.
Udi is a member of the European Speakers Bureau of the International .NET Association, an author and trainer for the International Association of Software Architects and a founding member of its Architect Training Committee. He is also a Dr. Dobb's sponsored expert on Web Services, SOA, & XML.
Presenting at international conferences like TechEd USA, SD Best Practices, DevTeach Canada, Prio Germany, Oredev Sweden, TechEd Barcelona, QCon London, and TechEd Israel - Udi covers in-depth mission-critical topics like durable services, persistent domain models, and multi-threaded occasionally connected clients.
Audience
This workshop is targeted at team leads, application and solutions architects, as well as technologists who are involved in making decisions about the overall system design of software products and projects.
Module 1: Distributed Systems Theory
Decades of distributed systems development have taught us many lessons. In this module we'll cover many historical mistakes as well as proven best practices for scalable and robust design. Topics include:
• 8 fallacies of distributed systems
• Transactions
Module 2: Coupling: Platform, Temporal, & Spatial
Loose coupling has become the watchword of complex systems development, yet few understand its multiple dimensions. In the module we'll be covering the three different dimensions of coupling as well as patterns for dealing with them.
• Platform Coupling - XML/SOAP
• Temporal Coupling - Synchronous/Asynchronous
• Spatial Coupling - Endpoints/Topics
Module 3: Asynchronous Messaging Patterns
Although scalability is achieved through the use of asynchronous message passing, more advanced message exchange patterns are required to handle today's complex integration scenarios. This module will cover the most commonly used patterns:
• One way
• Correlated Request/Response
• Publish/Subscribe
Module 4: Bus & Broker Architectural Styles
Enterprise Service Buses are all the rage these days. In this module we'll be covering what's the difference between the Bus architectural style, and the more well-known Broker, found commonly in many EAI projects. Topics will include:
• Architectural advantages and disadvantages
• Technological advantages and disadvantages
Module 5: SOA Building Blocks
One of the goals of SOA is to develop systems which are more closely aligned with Business. In this module we'll be covering an analysis methodology from moving from the business domain to executable systems that comply with all the principles of loose-coupling.
• Business Services
• Business Components
• Autonomous components & Queues
Module 6: Scalability and Flexibility
In order to enable agility, services must be able to scale up, out, and down quickly. In this module we'll see how autonomous components can be configured including transactional and durable aspects of message handling.
• Configuring autonomous components
• Scaling up and out
Module 7: Long running processes
The distributed communications patterns wouldn't be complete without a discussion on orchestration. In this module we'll see how to manage the state of long-running distributed communication flows as well as:
• Encapsulating process logic
• Advantages & disadvantages of orchestration
Module 8: Service / Autonomous Component Solutions
As developers go to implement autonomous components, guidance is required as to which concepts need to implemented in which project, what dependencies are there between projects, and how to bridge the worlds of messaging, business logic, and reporting. Topics include:
• Messages + Handlers
• Databases
Module 9: Service Layer - Domain Model Interaction
Logic-rich services require the use of advanced techniques for logic componentization. The Domain Model Pattern enforces a high level of Separation of Concerns, yet it must eventually be connected with Service Layer code that supports many concurrent users. In this module, the topics covered will include:
• Domain Model introduction
• Testing Domain Models
• Optimistic, Pessimistic, and Realistic Concurrency Models
Module 10: Creating High-Performance Domain Models
The strong separation between the Domain Model and the database which stores and retrieves its data may enable a high level of testability, yet often causes performance problems. In this module, we'll see the various aspects impacting the performance of persistence:
• Transactions and Isolation Levels
• Lazy Loading, Eager Fetching
• Databases Tips & Tricks
Module 11: Web Services and User Interfaces
The ease of interacting with users over the web drives the need for service to UI interactions. Also, many integrations require exposing synchronous web services to customers. In this module, we'll see what is required in both cases:
• ASP.NET 2.0 Asynchronous Tasks
• Rich Internet Applications and Services
• Web Services for integration
Module 12: Smart Client / Service Interaction
The publish/subscribe semantics with which services communicate require smart clients to perform a great deal of background work. Also, certain service contracts lead to more performant clients. In this module, we'll cover the first part of these interactions:
• Multi-threaded client challenges
• Client-friendly Service Contracts
• Service Agents and Client Repositories
Module 13: Notifications & Smart Clients
After Message Handlers in the Service Layer create or update the relevant Model objects in the client Repository, Supervising Controllers are in charge of getting Views to show the updated data. In this module, we'll describe the parts and interactions of these flows:
• Client-side Model Objects
• Supervising Controllers
• Views and their Interfaces
Module 14: Commands & Smart Clients
Capturing user intent and synchronization between views are at the core of smart clients. After describing solutions that use Events on the View Interfaces, the Command Pattern will be introduced to further decrease coupling between Supervising Controllers. In this module, we'll describe the parts and interactions of these flows:
• View Interfaces, and how Entity Cloning affects them
• Supervising Controllers and clone reconciliation
• Commands, and Event-Based programming
Monday, October 13, 2008 at 8:00 AM
- to -
Friday, October 17, 2008 at 5:00 PM (CT)
|
Headspring is the Leader in Agile Development. Download Headspring System's Approach to Delivering Quality Software On-Time and On-Budget Whitepaper and understand why. There are many different ways to engage with Headspring Systems in Agile software development. For clientele who would rather not or cannot maintain a staff of programmers, Headspring provides the code production by way software development consulting services. In consultation projects, the visions of the stakeholders are represented by on site clients and kept on track by subject matter experts (appointed by the stakeholders) who work side by side with Headspring developers. For business entities already undertaking in-house software development in need of better tools and better practices, coaching is available from Headspring. Our senior consultants are available to work onsite as coaches for extended engagements to teach Agile's edge. Finally, classroom and onsite training is another means to immerse the in-house programmers of our clients in the Scrum iterative organizational guidelines and eXtreme Programming technical standards of Agile. |
| View other Headspring Systems events |
|
|
Contact the Host |
|
|
Subscribe to receive notifications of future events by this host |
Email
Facebook
Twitter
LinkedIn
MySpace
Digg
del.icio.us
Reddit