Systems and methods for a mobile application architecture using backend-for-frontend in a tiered software framework

Non-transitory computer-readable tangible media that includes instructions for execution, which when executed by a processor of a computing device, is operable to perform operations comprising:

• receiving, by a mobile aggregator, a set of first messages over a wireless communication network from a frontend of the mobile application executing in a mobile device, the set of first messages comprising instructions in Remote Procedure Call (RPC) protocol to execute a feature of the mobile application, wherein:
• invoking the RPC protocol triggers suspending a calling environment in the mobile device and transferring procedure parameters across the wireless communication network from the mobile device to the mobile aggregator,
• the feature comprises one or more services of the mobile application executing in a cloud network,
• the set of first messages identifies the mobile aggregator as recipient, and
• different features of the mobile application are associated with respectively different sets of first messages;
• executing, by the mobile aggregator, the instructions in the first messages, wherein executing the instructions comprises:
• identifying, by the mobile aggregator, the one or more services of the mobile application called by the instructions in the first messages;
• generating second messages in another protocol compatible with communication in the cloud network;
• communicating, by the mobile aggregator, the second messages in the another protocol to the one or more services in the cloud network;
• receiving results from the one or more services;
• and
• generating a set of response messages with the results in the first protocol;
• and
• sending the set of response messages to the frontend, wherein:
• sending the response messages triggers unsuspending the calling environment and resuming execution at the frontend,
• and
• transaction history between any two of the first messages is stored in the frontend or in the one or more services.

An apparatus comprising:

• a processing circuitry;
• a memory storing data;
• and
• a communication circuitry, wherein the processing circuitry executes instructions associated with the data, the processing circuitry is coupled to the communication circuitry and the memory, and the processing circuitry and the memory cooperate, such that the apparatus is configured for:
• receiving, by a mobile aggregator, a set of first messages over a wireless communication network from a frontend of the mobile application executing in a mobile device, the set of first messages comprising instructions in Remote Procedure Call (RPC) protocol to execute a feature of the mobile application, wherein:
• invoking the RPC protocol triggers suspending a calling environment in the mobile device and transferring procedure parameters across the wireless communication network from the mobile device to the mobile aggregator,
• the feature comprises one or more services of the mobile application executing in a cloud network,
• the set of first messages identifies the mobile aggregator as recipient, and
• different features of the mobile application are associated with respectively different sets of first messages;
• executing, by the mobile aggregator, the instructions in the first messages, wherein executing the instructions comprises:
• identifying, by the mobile aggregator, the one or more services of the mobile application called by the instructions in the first messages;
• generating second messages in another protocol compatible with communication in the cloud network;
• communicating, by the mobile aggregator, the second messages in the another protocol to the one or more services in the cloud network;
• receiving results from the one or more services;
• and
• generating a set of response messages with the results in the first protocol;
• and
• sending the set of response messages to the frontend, wherein:
• sending the response messages triggers unsuspending the calling environment and resuming execution at the frontend,
• and
• transaction history between any two of the first messages is stored in the frontend or in the one or more services.