The Importance of Cache in T24 Applications

One topic that is rarely mentioned but extremely important in the world of APIs is the use of cache. To dive into the subject, let’s first understand what cache is.

A cache is a mechanism by which an application temporarily stores API responses or data to reuse them in subsequent requests, thereby avoiding repeated calls to the server and improving performance, latency, and resource consumption.

In simple steps:

1. The client (web, mobile, backend consumer) stores data previously obtained from an API.

2. If the same information is needed again and is still valid, it is retrieved from the cache instead of making another API call.

3. This reduces:

   • Response time

   • API load

   • Network usage

Cache in T24

For APIs in T24, there is a data caching process called warmup. In T24, this process stores the structure of responses, database connections, data types, catalogs, and other types of information in memory, making it immediately available when the client requests the API. It is worth noting that this cache is also automatically created after the first API request.

Example:

We have a service in our T24 API where we send a customer number, and it returns all the products and details the customer has (account number, product type, opening date, among others). The first time we retrieve this information, it can take up to 8 seconds. However, after executing the warmup, it only takes 1 second.

How much can cache improve performance in T24?

The best answer to this question is that it can improve response times by up to 85% on the first request to our service. This highlights the importance of using cache in our technological implementations.

Benefits of using Warmup in IRIS T24

• Improves system performance by preloading frequently used data and routines.

• Reduces response time during peak hours and system startup.

• Enhances user experience by ensuring smoother and faster transactions.

• Stabilizes the system after restarts or deployments.

• Minimizes first-transaction delays for critical banking operations.

• Supports business continuity by ensuring the system is fully ready before users begin operations.

At Performetriks, our experts are ready to help you implement the best possible cache configuration for your T24 core banking system. If you want to enhance the user experience with fast and efficient responses by implementing this functionality, don’t hesitate to contact us. At Performetriks, it will be our pleasure to assist you.

Happy Performance Engineering!

#T24 #CoreBanking #PerformanceTesting