Thus, the legacy apps should still have to be maintained by legacy engineers and they are not going away soon...Still a carrying cost to the company...until it decides to discontinue these legacy apps. And when it does stop those apps, BPM have to re-configure those business processes again to make since the SOA baseline was shaken...Why not get rid of legacy and go with the new technology to eliminate legacy costs for once.
@joeyhcmc Problem is, removing those apps may disturb more than just those apps! Think of legacy banking tx systems: zOS type cobol programs been running 10+ years. not to speak of the tx volume - then unmatched by MF. This was probably part of a huge multi-million dollar IS excercise for the bank. Thus 10+ years down the line, SOA/ESB comes in to tie in newer UNIX/Web applications. maybe when it's cost-efficient, they'll re-write legacy pieces with newer arch+If it aint broke, don't fix it!
Thus, the legacy apps should still have to be maintained by legacy engineers and they are not going away soon...Still a carrying cost to the company...until it decides to discontinue these legacy apps. And when it does stop those apps, BPM have to re-configure those business processes again to make since the SOA baseline was shaken...Why not get rid of legacy and go with the new technology to eliminate legacy costs for once.
joeyhcmc 2 years ago
@joeyhcmc Problem is, removing those apps may disturb more than just those apps! Think of legacy banking tx systems: zOS type cobol programs been running 10+ years. not to speak of the tx volume - then unmatched by MF. This was probably part of a huge multi-million dollar IS excercise for the bank. Thus 10+ years down the line, SOA/ESB comes in to tie in newer UNIX/Web applications. maybe when it's cost-efficient, they'll re-write legacy pieces with newer arch+If it aint broke, don't fix it!
darkbit1001 1 year ago