Abstract: Techniques are provided for automated localization of microservices. One method comprises obtaining, by a given microservice of an application, a message to be provided to a client device using an application programming interface (API) of the given microservice, wherein the message comprises a text portion having an identifier, wherein the text portion is in a first language; obtaining, by the given microservice, using the identifier, a translation of the text portion, maintained by the given microservice, in a second language associated with the client device; and presenting, by the given microservice, the message, with the translation of the text portion, to the client device using the API of the given microservice. Continuous integration aggregation techniques may be used to: (i) detect changes to localized files of the application; (ii) transform changed localized files to a file format; and (iii) store the changed localized files in a shared storage for translation.

Abstract: Techniques are provided for message content reduction using message templates. One method comprises obtaining a message of a given type, of multiple types, to be transmitted over a network; identifying one or more templates, of multiple templates, for the given type, wherein the templates comprise a respective message identifier; selecting a given template of the given message type based on a similarity of the message with the given template; updating the message by (i) incorporating the message identifier of the given template into the message and (ii) removing one or more fields of the message that match respective fields of the given template; and transmitting the updated message to a recipient device. The recipient device may determine whether the updated message comprises the message identifier, and may retrieve a message template using the message identifier. The recipient device may store the updated message as a template in a message cache.

Abstract: A system can identify microservices calls. The system can, in response to identifying a first call, where the first call originates externally, storing, to logged calls, a first association between the first call, a response to the first call, a first entity that originated the first call, a second entity to which the first call is destined, a unique identifier, and a counter associated with the unique identifier, or where the first call originates internally, storing, to the logged calls, a second association between the first call, the response, the first entity, the second entity, the unique identifier, and the counter after incrementing the counter, wherein the unique identifier is identified by the first call. The system can order logged calls that share unique identifiers according to values of respective counters. The system can store a topology of the microservices that is generated according to the ordered logged calls.

Abstract: A mobile money system comprising: at least one mobile money device configured with at least a CPU, a GSM engine, antenna, display, keypad/touchpad, printer and SIM reader; and at least one external SIM card configured to be read by the reader; wherein the mobile money device uses a SIM Tool Kit application stored on the external SIM card to process at least one mobile money transaction.