DisclaimerThe words and opinions expressed here do not represent the opinions or views of my employer or anyone associated with me in any way.
Tag Archives: SOA
I will be speaking at the Richmond Code Camp on Saturday, October 6, 2012. The event is taking place on the campus of University of Richmond and you can find all of the details for the event here. My presentation … Continue reading
If you are writing anything more than a basic web service that is hosted on IIS, I highly recommend gaining a firm understanding of Windows Server AppFabric. The recently released Microsoft Windows Server AppFabric Cookbook is the perfect resource to kick-start the learning process for the uninitiated and act as the go-to reference guide for the experienced architect. Continue reading
Picking up where we left off in the Service Bus Introduction, this post will walk through a Relayed Messaging sample in order to highlight how the AppFabric Service Bus could be utilized to build Hybrid applications. In addition to the basic sample, I will also demonstrate how to provision a BizTalk Server 2010 Receive Location on the Service Bus.
I recently had the honor of delivering a presentation entitled “Build Hybrid Applications Using the Azure AppFabric Service Bus” at the Richmond and Philly.NET Code Camps. Virtually no one in either of the sessions had any previous experience with Windows Azure or the components of the AppFabric. In this series of blog posts, I will expand upon the presentation in an effort to introduce the AppFabric and take a deeper dive into the code and practical application of the Service Bus messaging patterns.
During my past BizTalk engagements, I have had the opportunity to work closely with my clients in developing flexible and maintainable applications. One of the most common issues that I come across is the misuse of some of the shapes available within the Orchestration Designer. By misuse, I simply mean to say that many BizTalk developers will drag and drop shapes into an orchestration to implement the business process, but do not take into account the implications of doing so. More often than not, the result of selecting the wrong shape for the job is not seen until the application is tested or even worse, the production environment. One of the primary reasons that BizTalk is used is the opportunity to build loosely coupled, flexible and scalable applications. By choosing the wrong shape, many developers will wind up doing exactly the opposite, thus setting the application down the course of tight coupling and brittle implementation. In this post, I am going to highlight two of the most often misused shapes, Call Orchestration and Start Orchestration, explain when they should be used and provide an alternate technique to overcome their shortcomings.