I like the CICS approach, particularly since you already have it implemented, know how to monitor/manage/secure it, etc. It's a very natural fit for many environments and for most developers working in this domain. CICS has also had a solid track record of picking up new Web Services capabilities as the standards have evolved, so you get that free as you track new CICS releases. Same with performance improvements. And CICS neatly takes care of that persistence issue that was mentioned.
When is CICS ever (completely) down, by the way? Alternatively, is it better to worry about just keeping at least a bit of CICS up and running (which you presumably already worry about) versus keeping both CICS and something else up and running? I would contact IBM and also cross-post to the CICS-L list to ask for advice on performance engineering and tuning to see if there's anything you're missing. Every once in a while it's worth checking performance for best practices, regardless of solution approach. -------------------------------------------------------------------------------------------------------- Timothy Sipples Resident Enterprise Architect (Based in Singapore) E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
