24:00 What they don't mention here, and what they don't mention almost anywhere, is a really important requirement of the Knative container contract that Cloud Run inherits: containers have dramatically throttled CPU outside the scope of a single request. That means that between starting up your server and handling the first request, you can't do anything. You have to initialize all your variables and everything AFTER you start handling the first request. This is almost impossible to debug if you don't know about it, so it's very frustrating that it's almost never mentioned.
An application also includes user interface and database. More often than not a database already contains few million data. How do these two elements participate with this type of architecture transition
24:00 What they don't mention here, and what they don't mention almost anywhere, is a really important requirement of the Knative container contract that Cloud Run inherits: containers have dramatically throttled CPU outside the scope of a single request. That means that between starting up your server and handling the first request, you can't do anything. You have to initialize all your variables and everything AFTER you start handling the first request. This is almost impossible to debug if you don't know about it, so it's very frustrating that it's almost never mentioned.
An application also includes user interface and database. More often than not a database already contains few million data. How do these two elements participate with this type of architecture transition
great!
cool!