I had a nice dinner yesterday night with Don Box, Ingo Rammer, Christian Weyer, Christian Nagel, Benjamin Mitchell, Matt Tavis, and Juval Löwy. Don arrived a bit later and started by saying "look, I wanted to have dinner with all of you because we've decided to make some changes to Indigo and by now we've decided to simply bake WSE into Longhorn". Silence. Laughter. No, we didn't buy it...
On cool aspect about TechEd Amsterdam is that it is essentially a home game for newtelligence in terms of proximity to home-base and it’s one of the very few conferences that I can drive to (I’ve spent way too much time in airports and on planes this recent half year). Saturday it took me just 1:50h to get here from my place near Düsseldorf.
Part of the fun is...
Finally, finally, finally. It was a looong wait. As many others, we were in a wait loop for WSE 2.0 for a long time and that let us do what we do today only much, much later than we initially anticipated. So after being able to test on and adjust for the WSE 2.0 RTM bits for the last four weeks, we're now happy enough with our "1.0" that we're ready to share it:
Microsoft EMEA and newtelligence AG present:...
After providing some background on what nodes and networks are and how they work, I’ll get to how they are configured. Warning: This post is pretty dense in terms of content ;-)
Each FABRIQ network is defined in a single configuration document with the root element “fabriq”.
A network defines a group of nodes that exchange messages. The network defines a trust perimeter in regards to security and behavior around a set of nodes and is the smallest unit of configuration in FABRIQ. Nodes inside a FABRIQ network should not be exposed to and should not directly addressable from entities outside the network. Securing a FABRIQ network...