Middleware and Routing
Discussion
I am a Middleware architect type in one of my careers and I am working on a project at the moment where I am in a minority in my viewpoint....
We are specifying a large Europe wide private network secured at each entry point (not saying how as NDA's preent me)...
My thoughts on the matter are thus and I would have thought common sense would support it.
If you build a large secure private network, my fundemental requirement for messages entering said network would be that they are addressed at point of entry and that the format (if format is an issue) at the point of entry also...
why oh why would anyone wish to allow any old crap to get to the core infrastructure and promise all singing and dancing routing and message validation.
Edge based routing and syntax validation surely is the only valid architecture in this case?
We are specifying a large Europe wide private network secured at each entry point (not saying how as NDA's preent me)...
My thoughts on the matter are thus and I would have thought common sense would support it.
If you build a large secure private network, my fundemental requirement for messages entering said network would be that they are addressed at point of entry and that the format (if format is an issue) at the point of entry also...
why oh why would anyone wish to allow any old crap to get to the core infrastructure and promise all singing and dancing routing and message validation.
Edge based routing and syntax validation surely is the only valid architecture in this case?
Is this point-to-point connectivity or does it go into some kind of central hub/broker to provide the routing? If it was point-to-point with lots of different message formats, etc, I'd tend to put the messages into a common form at the entry points, route it accordingly, and then retrieve the messages at the exit points in the required format. Alternatively, if they were going through a central hub, then let that do all the validation/transformation/routing work (assuming it's up to the messages volumes, etc) centrally.
Fancy saying what message transport you are using for this project?
Cheers, James.
Fancy saying what message transport you are using for this project?
Cheers, James.
aldi said:
Dunno if I've understood but perhaps they're taking the view that sooner or later, someone will bypass the edges?
If the edge routing blocks all messages that do not conform to a) routeing rules and b) syntax/format rules then you're theoretically protected from malicious messages and relieve the internal infrastructure of the weight of unwanted traffic.
Negative side is greater efforts in admin and cofiguration. Possible issues with routing to new internal nodes and adding new formats to the messaging...
iaint said:
guydw said:
are you talking about IP routing ? Or some other kind of routing.....
Guessing but it'll be business messages (SOAP/CORBA maybe) over a secure IP network... The routing will be to make sure a request for service 'A' gets to the provider of service 'A'...
possibly
.... problem being customers have been told the service will offer an all singing dancing service where they can just chuck things down various secure interfaces and forget about it... utter nonsense in my opinion.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff