receiving requests via a client application interface (API) coupled to the mainframe system to consume or publish data by the applications, wherein the requests can be sent in any protocol;

determining by the client application API a messaging service to be used based on the received requests;

converting via the client server database the received requests into processes of a plurality of processes of the plurality of messaging services based on the messaging service to be used and a configuration that is based on the client application API's determination of which messaging service is to be used, wherein the client server database is read using a queue name as a key and a request from a messaging abstraction (MAB) trigger abstraction API to get the messaging service details to determine the messaging service status, and wherein the plurality of processes include MQ Get, MQ Put, Kafka subscribe, Kafka publish, and MQ and Kafka together; and

transmitting via a server application interface (API) coupled to the mainframe system the converted received requests to endpoints as defined by the requests, wherein the endpoint remains unchanged when the protocol that the request was sent in is different than a protocol used by the selected messaging service.