Hi,
While working with a customer, I just came across one usecase:
As per AS-IS architecture, customer uses MS-SQL/MS-Stored Proc to fulfill the needs of their use cases. Hence, the business logic has been completely written in the SQL/SP only. To achieve this, various source systems are calling the SP/SQL.
Now in the TO-BE architecture, middleware needs to come in between Source systems and target system( target to be replaced from DB to various services like webservices, JMS, Oracle DB table VIEWs etc).
Since customer is not willing to change in their source technology, I suggested them to invoke the same signature based new SP deployed in Oracle DB(so I can use utl packages to call webservice from it to invoke the middleware services). But later I heard that they can do this unfortunately for some internal source applications only and not for all.
Is there any possible approach that can help me calling the middleware by having the very minimal changes in source systems technology/integration-approach? Your valuable suggestions/design approach will be highly appreciated.
Thanks,
Vikas