SOA patterns - Reservations

Posted by: Cirrus Minor, on 08 Sep 2009 | View original | Bookmarked: 0 time(s)

1.1 Reservation When you use transactions in traditional n-tier systems life is relatively simple. For instance, when you run a transaction and an error or fault occurs you abort the transaction and easily rollback any changes getting back your system-wide consistency and peace of mind. The reasons this is possible is that a transaction isolates changes made within it from the rest of the world. One of the base assumptions behind Transactions is that...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.

Similar Posts

  • Take Caution with WinForms DataGridView RowPrePaint more
  • Data Access Guidance more
  • Exposing Custom WCF Headers through WCF Behaviors more
  • "The security validation for this page is invalid" when calling the SharePoint Web Services more
  • Udi Dahan's Advanced SOA course now discounted under $2000 more
  • SOA - Between philosophy and concrete answers more
  • SOA Patterns Book Status Update more
  • Digitally Signing an XML Document and Verifying the Signatures more
  • Book Review: Implementation Patterns more
  • Clean up your SOAP-based Web services more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD