Technologies for scaling user interface backend clusters for database-bound applications

One or more computer-readable storage media comprising a plurality of instructions stored thereon that in response to being executed cause a user interface (UI) application server of a plurality of UI application servers of a UI backend cluster to:

• perform, by a UI application manager of the UI application server, a data read operation, wherein the data read operation comprises to:
• retrieve a session sequence ID associated with a present user session, wherein the session sequence ID corresponds to a first master database sequence ID received from a master database manager of a master database server of the UI backend cluster during a most recent write operation of data to a master database of the master database server during the present user session;
• read, in response to a determination the session sequence ID is not empty, a local database sequence ID from a local read-only database associated with UI application manager, wherein the local database sequence ID corresponds to a second master database sequence ID received from the master database manager during a most recent asynchronous replication of the master database to the local read-only database, and wherein the local read-only database comprises an asynchronously replicated copy of the master database;
• and
• determine whether the session sequence ID is less than or equal to the local database sequence ID;
• read, subsequent to a determination that the session sequence ID is less than or equal to the local database sequence ID, the data from the local read-only database;
• and
• transmit by the master database server to the UI application server, a data modification operation status wherein the modification operation status indicates the data from the local read-only database is stale;
• determine, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, whether a threshold duration of time has elapsed since having received the indication;
• and
• perform, by the UI application manager and in response to a determination that the threshold duration of time has elapsed, another data read operation;
• and
• transmit, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, a data read request to a master database manager of the master database server, wherein the data read request is usable by the master database manager to query the master database to retrieve the data associated with the data read request from the local read-only database to retrieve the applicable data from the master database.

A user interface (UI) application server of a plurality of UI application servers for scaling UI backend clusters for database-bound applications, wherein the UI backend clusters include the plurality of UI application servers and a master database server, the UI application server comprising:

• a CPU;
• and
• a memory having stored therein a plurality of instructions that when executed by the processor cause the UI application server to:
• perform, by a UI application manager of the UI application server, a data read operation, wherein the data read operation comprises to:
• retrieve a session sequence ID associated with a present user session, wherein the session sequence ID corresponds to a first master database sequence ID received from a master database manager of the master database server during a most recent write operation of data to a master database of the master database server during the present user session;
• read, in response to a determination the session sequence ID is not empty, a local database sequence ID from a local read-only database associated with UI application manager, wherein the local database sequence ID corresponds to a second master database sequence ID received from the master database manager during a most recent asynchronous replication of the master database to the local read-only database, and wherein the local read-only database comprises an asynchronously replicated copy of the master database;
• and
• determine whether the session sequence ID is less than or equal to the local database sequence ID;
• read, subsequent to a determination that the session sequence ID is less than or equal to the local database sequence ID, the data from the local read-only database;
• transmit, by the master database server to the UI application server, a data modification operation status wherein the modification operation status indicates the data from the local read-only database is stale;
• determine, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, whether a threshold duration of time has elapsed since having received the indication;
• perform, by the UI application manager and in response to a determination that the threshold duration of time has elapsed, another data read operation;
• and
• transmit, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, a data read request to a master database manager of the master database server, wherein the data read request is usable by the master database manager to query the master database to retrieve the data associated with the data read request from the local read-only database to retrieve the applicable data from the master database.

A method for scaling user interface (UI) backend clusters for database-bound applications, wherein the UI backend clusters include a plurality of UI application servers and a master database server, the method comprising:

• performing, by a UI application manager of a UI application server of the plurality of UI application servers, a data read operation comprising:
• retrieving a session sequence ID associated with a present user session, wherein the session sequence ID corresponds to a first master database sequence ID received from a master database manager of the master database server during a most recent write operation of data to a master database of the master database server during the present user session;
• reading, in response to a determination the session sequence ID is not empty, a local database sequence ID from a local read-only database associated with UI application manager, wherein the local database sequence ID corresponds to a second master database sequence ID received from the master database manager during a most recent asynchronous replication of the master database to the local read-only database, and wherein the local read-only database comprises an asynchronously replicated copy of the master database;
• and
• determining whether the session sequence ID is less than or equal to the local database sequence ID;
• reading, subsequent to a determination that the session sequence ID is less than or equal to the local database sequence ID, the data from the local read-only database;
• transmitting, by the master database server to the UI application server, a data modification operation status wherein the modification operation status indicates the data from the local read-only database is stale;
• wherein reading the data from the local read-only database comprises transmitting a data read request to a database manager of the UI application server, and further comprising querying, by the database manager, the local read-only database to retrieve the data corresponding to the data read request from the local read-only database;
• determining, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, whether a threshold duration of time has elapsed since having received the indication;
• and
• performing, by the UI application manager and in response to a determination that the threshold duration of time has elapsed, another data read operation;
• and
• transmitting, by the UI application manager and subsequent to having received an indication that the reading of the data from the local read-only database was unsuccessful, a data read request to a master database manager of the master database server, wherein the data read request is usable by the master database manager to query the master database to retrieve the data associated with the data read request from the local read-only database to retrieve the applicable data from the master database.