QUOTE(Jkan2021 @ Aug 8 2024, 08:51 AM)
Thanks for this! Last night, I experienced it first-hand (i.e payment made after 10pm). But upon reading your comments, this made me feel at ease. I called the UOB customer service this morning and yes, they mentioned that cc payments made after 10pm will only be reflected 24 hours in the app. Apparently, something to do with system maintenance. Then I proceeded to ask the guy until what time is this daily maintenance of theirs? The fella also not sure and recommended me to make future payments outside of the 10pm-6am window. Having said that, I did get an SMS last night from UOB saying that they received my payment amount -- problem is the online banking transactions will only be reflected 24 hours later.
I've a CIMB cc and I don't have such issues. As for this UOB cc, I'll have to remind myself to make future online payments during the daytime.... which is mildly annoying IMO. Shouldn't online banking be flexible? Oh well...

in the online or cloud services, we are expecting all services to run in real-time. that's ideal but not practical.
not all systems need to run real-time, every time, 24/7/365-6. some can be delayed slightly.
by reducing some non-critical services to run in full real-time, this will save the infra cost and load to their systems --> increase service availability and reliability.
there is no such thing as infinite speed, inifinite resources, infinite system bandwidth, etc. the more you ask for it, the more you need to pay.
example like LRT/MRT train. from Point A to Point B, ETA is 10 minutes, provided speed is consistent but safe.
Of course adding throttle will speed up the journey, but also increases risks and other issues

eg passengers getting nausea or injured when the coach speeding like a demon just to be "faster".
so, some systems (or in this example), some track section, the coach need to slow down. some section, they can speed up safely.
again, diff bank has diff requirements to manage their systems.