I've been reading up on Biztalk recently (i've never used it in production) i've always been vaguely interested/aware of it since seeing it used as part of a demo in the vs2005 launch tour. Whilst i've been reading up on biztalk i've been trying to think about how it would fit into my company's current architecture.
Due to the nature of my companies IT history (which i'm not going to go into here) We have a lot of little self contained applications that essentially move data from one location to another and do some parsing/transformation in the process. In my mind i can easily imagine these being replaced by biztalk orchestrations, then using the admin/portal features to give us a single enterprise control panel to check the health/success/failure of the constituent parts.
but theres a question thats been hanging around in my head whilst i've been thinking about this. What things need to be considered before making the move from a bespoke app to a biztalk orchestration?
For me 2 of those things are:
Performance of bespoke app vs biztalk replacement?
Maintainability of bespoke app vs biztalk replacement? (is it any more difficult picking up a bespoke c# app than it is to learn biztalk)
However at the moment, despite my reading, i'm not sure whether i can answer either of these sub-questions