Contents tagged with WCF
-
South Florida BizTalk User Group: Improving agility with the ESB 2.0 toolkit
Next Tuesday (November 10th) my colleague Uri Katsir will be presenting a session at the South Florida BizTalk Users Group about improving agility in large BizTalk environments using the ESB toolkit. If you are a BizTalk developer or operations architect working on complex BizTalk deployments you MUST attend Uri's session. In order to keep things in perspective, Uri has prepared a series of interesting demos that illustrate the techniques used to improve the development and management experience of BizTalk solutions by leveraging the ESB toolkit. The presentation is 100% focused on real world scenarios including some of the lessons Uri has learned while working on one of the most complex BizTalk environments in the world.
-
Uri Katsir is blogging!
My friend and colleague Uri Katsir just joined the blogosphere. Uri is a BizTalk wizard who is currently working on one of the biggest BizTalk implementations in the world. We are extremely proud to have him as part of our technical staff at Tellago. Uri has already posted a couple of interesting write-ups about ESB itineraries troubleshooting and deployment techniques.
-
The WCF Extensibility Guidance is now on MSDN!
As the WCF team already announced, the first chapter of the WCF Extensibility Guidance is now available on MSDN . This paper is the result of an effort I started a few months ago with my colleague and friend Pablo Cibraro. Our goal was to provide a detailed guidance of the major extensibility points of the WCF runtime. In that sense, we decided to cover major areas of the WCF extensibility programming model such as channels, client-dispatcher, security, hosting, metadata, RESTful service and even the new extensions on WCF 4.0.
-
Implementing a custom RSS/Atom adapter with Microsoft StreamInsight
In a previous post we explained the programming model of Microsoft's StreamInsight adapter framework. The fundamental capability of this framework is to streamline the flow of events in and out of the StreamInsight hosting application. One of the main advantages of this model is that enables developers to create their own adapters that can be leveraged on StreamInsight-based solutions. On this post we will explore the details of implementing an RSS/Atom adapter using StreamInsight's adapter framework.
-
Exploring StreamInsight's adapter model
Adapters are a fundamental component of Complex Event Processing (CEP) applications. In a nutshell, adapters provide the interfaces that abstracts how events are produced or consumed by the CEP infrastructure. Most CEP frameworks leverage the concept of an adapter as the fundamental mechanism for interacting with heterogeneous systems. Following the same principles, Microsoft's StreamInsight uses adapters to model the flow of events in or out of the CEP host. Furthermore, StreamInsight enables a flexible programming model that allows developers to extend the core infrastructure by implementing custom adapters. From a programming model standpoint, StreamInsight classifies adapters based on the direction of event flow and on the event model used.
-
Looking for an ASP.NET/AJAX developer
My company Tellago, Inc is looking to hire an experience ASP.NET/AJAX developer for a six months contract gig in Florida. Candidates should also have knowledge of WCF, ADO.NET Entity Framework and ADO.NET Data Services. You will be working in a highly dynamic team lead by some of our top architects. If you are interested please drop me a line at jesus dot rodriguez at tellago dot com.
-
Processing events from multiple sources using Microsoft StreamInsight
One of the fundamental patterns of Complex Event Processing (CEP) applications is the ability of process events from various input sources and distribute to multiple output sources. These operations require high degrees of coordination what makes it particularly difficult to implement in real world scenarios. Why is that? Well, for starters, continuously querying data from multiple sources entails implementing certain degrees of parallelisms on the CEP application. As we all know, parallel processing techniques typically introduces challenges from the error handling and availability perspective. These complexity is increased on CEP scenarios that need to create queries that combines events from multiple sources that are being produced in parallel. The following figure helps to illustrate that scenario.
-
Microsoft’s StreamInsight first thoughts
I spent this weekend toying with Microsoft StreamInsight bits. I have a few blog posts planned for the next few days that tackle very specific CEP patterns but I figure it might make sense to start by highlighting some of the features I think differentiate Microsoft's StreamInsight from other CEP technologies in the market. Here is a n initial summary of the features I really like about Microsoft's StreamInsight:
-
Speaking at ArcSig User Group tomorrrow
I will be speaking tomorrow at the South Florida Architecture User Group (ArcSig). The session is titled From SOA to WOA: Introducing Web Oriented Architectures and touches upon the fundamental principles and architecture techniques that can help developers to implement distributed systems that leverage the principles of REST.
-
My thoughts about RETRO: A RESTful Transactions Model
Transactions has typically been one of the aspects that the WS-* followers continuously point out as one of the weaknesses of the REST model. Even though we all agree that atomic transactions in distributed systems are JUST A BAD IDEA and everybody that follows Werner Vogels's lectures knows that the eventually consistent model is the way to go, we can't deny that transactions (conceptually) are an important part of everyday's business processes. However, let's just all be on an agreement that conceptual transactions don't necessarily have to be implemented as atomic transactions and there are simpler and more scalable models that have been successfully adopted by the industry. The RESTful model is not an exception to that rule and consequently we need an efficient way to model transactions without violating the principles of REST.