In the view of Oracle Vice President of Server Technology Amlan Debnath, the last ten years have witnessed “a tremendous shift” toward real-time service oriented architectures.
And during ebizQ’s Optimizing Business Processes in Real-Time with Event-Driven Architecture webinar, the second in the Oracle-sponsored Creating an Integrated Enterprise Webinar series, Debnath presented an end-to-end integration methodology for creating a real-time service-oriented architecture.
“As Charles Darwin has put it blithely, ‘It is not the strongest of the species that survives, nor the most intelligent, but the one that is most responsive to change.’ And that's exactly what you have to do,” he noted.
“You cannot incorporate all the events, all the business processes, all the services on Day One; you have to prioritize and figure out where you'll get the best bang for your buck,” noted Debnath, who offered a methodology for creating an event-driven service oriented architecture.
The step-by-step process includes:
Defining Business Events: Providing a common view of data and decoupling systems to make it easy to add, upgrade, and migrate them. “When an order is entered, and suppose this order was entered in a CRM system like Seybold, it has a certain presentation of how the order looks. But that is not how all of your different systems think of an order,” Debnath noted.
A common, canonical data model for business events enables companies to “isolate your different systems from each other and link them to one common model, so when something changes in one of the systems, the only thing that you have to change is that particular interaction and nothing else.”
Exposing Business Functions as Services: Debnath urged companies -- especially those using different systems -- to opt for intermediary interfaces ”to
expose my business functions and services in a standard way. So anyone accessing these services from our side does not have to know how Seybold works or how Oracle Apps works, etc.”
Linking Events and Services to the Process: Linking events, services, and processes to each other yields results similar to “where two pieces of metal come together, and suddenly there's magic -- and what happens here is when the events and the services come together, suddenly you have a working model of your business process that you go and deploy and use in your systems.”
-1-