rickgaribay.net

Space shuttles aren't built for rocket scientists, they're built for astronauts. The goal isn't the ship, its the moon.
posts - 303, comments - 180, trackbacks - 35

My Links

News

Where's Rick?


AgileAlliance deliver:Agile 2019- 4/29
Desert Code Camp, PHX - 10/11
VS Live Austin, TX - 6/3
VS Live SF - 6/17


About Me
Hands on leader, developer, architect specializing in the design and delivery of distributed systems in lean, agile environments with an emphasis in continuous improvement across people, process and technology. Speaker and published author with 18 years' experience leading the delivery of large and/or complex, high-impact distributed solutions in Retail, Intelligent Transportation, and Gaming & Hospitality.

I'm currently a Principal Engineer at Amazon, within the North America Consumer organization leading our global listings strategy that enable bulk and non-bulk listing experiences for our WW Selling Partners via apps, devices and APIs.

Full bio

Note: All postings on this site are my own and don’t necessarily represent the views of my employer.



Check out my publications on Amazon Kindle!





Archives

Post Categories

Published Works

Intra-Process Communication Transport

I met Roman Kiss in person at the MVP Summit today, and had a great conversation about how to provide an intra-process solution when performance is critical and you don't want to pay for the creation of transport channels unless you absolutely have to.

Roman has done a fantastic job documenting this on CodeProject: http://www.codeproject.com/KB/WCF/NullTransportForWCF.aspx

The idea is that even IPC requires necessary transport channel creation to marshall between processes. The Null Transport, as Roman calls it, provides communication within the same Application Domain. So, it isn't as close to the metal as you can get, it *is* bare metal.

This is a brilliant approach to providing intra-process communication within SOA while providing the same level of flexibility that any WCF client/service gets via binding/transport choices that are, for the most part, post-depoloyment decisions.

 

Print | posted on Monday, April 14, 2008 5:56 PM | Filed Under [ WCF ]

Feedback

Gravatar

# re: Intra-Process Communication Transport

Good stuff! We have had cases were we need the performance of direct calls, but also realize the calculations and logic were a good service candidate. This solves a significant problem we had and had the potential for too much code to make it into the client (in this case a thick client app). In our case we had a datagrid that showed some financial calculations for 200-300 items. If a finance parameter changed the calculations would have to run for all items. Thanks for the post!
4/23/2008 6:39 PM | Brendon Birdoes
Gravatar

# Sitting in an Oslo SDR

<p>That's all I am allowed to say but I am very encouraged. Also, as one of my Connected Systems collegues, Rick Garibay, states , there is a lot of sheer talent in the room like Juval Lowy, Brian Loesgen, Brian Noyes, Michele Leroux Bustamante, Roman Kiss, Don Box, the Sells brothers. Also check out Roman...</p>
12/2/2008 3:22 PM | Sam Gentile's Blog
Comments have been closed on this topic.

Powered by: