None of the main live patching solutions (Ksplice, kpatch, kGraft) are really "zero downtime", just "deferred downtime"... patch now, reboot later (i.e. an outage window is mandatory, Ksplice/kpatch/kGraft does not avoid it)... if it's a 24/7 system and patching can't wait until a regular/scheduled outage window then you probably want live patching... but then, if it's a 24/7 system why doesn't it have some redundancy designed in?... innodb clusters (MySQL), Data Guard or RAC (Oracle), AlwaysOn (MS-SQL)... or, for non-database servers, redundant webservers and file servers fronted by load balancers etc...
Ksplice is available for Oracle Linux, free of charge, for Oracle Linux customers with a Premier support subscription (3)
Ksplice can patch almost any part of the kernel, while kpatch can only patch functions. (2)
Ksplice offers user space patching, which allows users to patch critical components such as glibc and openssl. (2)
Ksplice also offers more comprehensive safety checks to ensure that users cannot call removed functions. (2)
Ksplice cannot patch applications that use either setcontext or swapcontext from glibc to perform user space context switching between process threads. (1)
Because of certain kernel limitations, Ksplice does not patch the init process (PID 1 ). (1)
Only patches kernel functions