The reality is that Systems of Record applications have to prepare for an onslaught of requests from modern Systems of Engagement applications. And the way you have exposed your services and allowed integrations in the past simply won’t work in the new model. New digitally disrupting applications speak a different language (REST), can come to you from multiple locations (web, mobile, device, third party services) and go from 5 requests per second to 5 million without forewarning. This doesn’t mean you have to radically rethink your Systems of Record or that you have to redesign them in modern architecture, but you do have to start turning them into more modern, consumable services — and that’s the radical change.
While your Systems of Engagement may or may not become discrete software services that your customers tap directly, your Systems of Record will be software that the Engagement layer consumes. And if these capabilities can’t be integrated easily or speak the right language your developers, who are driven by agility and the need to deliver business value by any means possible, may build their own back-end services, or leverage third party services which create integration and records reconciliation nightmares.
Don’t let this happen inside your walls. The sooner you can acknowledge the ground is shifting beneath your company, the sooner you can prepare your systems of record to handle the effects. My new report, “The Seismic Shift in Application Portfolios,” details the emerging best practices that are helping the leading companies in The Age of the Customer deal with this change. It’s not radical but its new and necessary.
Source: Computerworld UK
Sign up for CIO Asia eNewsletters.