Article suggests that a high performance framework is implemented where notification of a unavailability will be propagated "before real user tried to execute a request" (which would have 50% probability of happening if number of heartbeats per second would be equal to number of requests per second the service serves, ha ha). Also from the Article we can learn that sending a 304 with content does not work as expected (!?)
Not only that, but there should be only one connection to database, through all traffic will go. Pulling that up through a network switch connected to a server with multiple cables, or pushing all that through a single TCP connection, with a foot note that advises against rewriting it after a few years?
Also, everything explained there should run in a single thread, because surely it will be fast enough.
Good luck with that.
[if you find other funny stuff that I missed, leave them in the comment section below]
Not only that, but there should be only one connection to database, through all traffic will go. Pulling that up through a network switch connected to a server with multiple cables, or pushing all that through a single TCP connection, with a foot note that advises against rewriting it after a few years?
Also, everything explained there should run in a single thread, because surely it will be fast enough.
Good luck with that.
[if you find other funny stuff that I missed, leave them in the comment section below]