Multiplatform microservice connection techniques
Inter-microservice communications are managed through in-memory connection routing. A sending microservice writes a message over a port associated with the connection. The message is routed directly to one or more receiving microservices associated with the connection over their ports associated with the connection. The message may be converted to a different format or multiple different formats through plugins processed when the message is received over the sending microservice's port and before the converting messages are routed over the receiving microservices' ports. The inter-microservice communications are hardware and platform independent or agnostic, such that the microservices associated with the connection can be processed on different hardware and different platforms from one another.
1. A method, comprising:
establishing an in-memory connection between microservices associated with multiple platforms, wherein establishing further includes creating an in-memory mapping between addresses associated with the microservices for the in-memory connection, wherein creating further includes assigning each microservice a communication port for use during the in-memory connection and adding port assignments for each microservice to the in-memory mapping, wherein assigning further includes adding plugin identifiers assigned to the at least one plugin and selectively associated with the microservices and adding plugin assignments for selective ones of the microservices within the mapping;
receiving a message from a sending microservice associated with a first platform during the connection;
calling at least one plugin associated with at least one second platform to translate the message from a first format to at least one second format; and
routing through the in-memory connection the message in the at least one second format to at least one receiving microservice associated with the at least one second platform.
2. The method of claim 1 , wherein receiving further includes monitoring the communication ports associated with the port assignments and identifying the sending microservice when the message appears over an assigned port associated with the sending microservice as defined in the port assignments of the in-memory mapping.
3. The method of claim 2 , wherein calling further includes identifying the at least one receiving microservice as remaining ports associated with the port assignments that are not the assigned port associated with the sending microservice as defined in the port assignments of the in-memory mapping.
4. The method of claim 3 , wherein identifying further includes obtaining a corresponding plugin identifier for each of the at least one receiving microservice from the in-memory mapping.
5. The method of claim 4 , wherein routing further includes obtaining as output from the at least one plugin the message in the at least one second format and providing over the corresponding remaining ports to the corresponding at least one receiving microservice.
6. The method of claim 1 further comprising, processing the method when a transaction is initiated at a transaction terminal.
7. The method of claim 6 further comprising, providing the in-memory connection for interaction between the microservices during the transaction in order to provide the transaction with one or more of: a transaction service, a security service, a reservation service, a financial service, a payment service, and a loyalty service.