Build better T24 APIs with this best practice guide covering everything from input validation to performance and documentation.

When banks migrate to new core banking releases or publish new products, their main concern is the reliability of their platform.

The good old saying that we unlock our greatness by working on the hard things is true for our personal development and T24 core banking systems. Of course, like in any complex system, we have thousands of tuning options. But, the science, or some call it art, in our business is really to find the optimal balance that brings out the best system performance and throughput of your Core Banking engines.

Waiting for something for a long time can be very frustrating. As a human, a waiting time of up to 3 seconds is okay. We get frustrated between 3 and 5 seconds, and processing times beyond 8 seconds result in a massive loss of engagement.

Reading and writing data to large files is often a performance bottleneck, which is also true for the T24 core banking system. Usually,...

In one of my assignments, critical services of a core banking engine were crashing every day. Engineers of this significant bank were...