As mentioned previously a **Middleware** is part of a set of techniques capable of interconnecting different systems regardless of the technology in which it was developed or the final function of each tool.
The middleware has multiple advantages that can be applied to your type of business in a personalized way, among the advantages we can highlight:
- **Easy to implement**
- **Improves query response times**
- **Save investment resources**
- **Secure interconnectivity**
**But, How do we deal with unique and consecutive ids during the integration of two or more platforms?**
A middleware acts as a communication bridge between systems an /or platforms, it must always have an entity within its structure that identifies (translates) each unique key within the involved (systems and/or platforms).
In this way, each time an action that requires a "key" is executed, the middleware will be able to identify or map it on each of the other platforms, providing the required response in the shortest time possible and without complications.
For example,
system1
key name
rupe rupertino
system 2
key name
cleo reutilia
middleware
key system s_key f_key
1 1 rupe cleo
2 2 cleo rupe
As you can see, what exists in system 1 and 2 has a key identified in the middleware but with different names.
At the moment that system 1 asks the middleware for the name of the key rupe in system 2 and when passing through the middleware will see that the s_key = rupe in system 1 and will take the key f_key = cleo asking the system2 for the key = cleo and system 2 will respond with the name = reuses what it will return to the middleware and the middleware will send it to system1 so that the communication is done **quickly, effectively and securely.**
We can conclude that to achieve a **successful implementation** of your applications with the middleware you will be able to determine unique keys for each system, providing an optimal translation when inquiring with your users.