s1m0nw1
11/21/2019, 7:19 AMnfrankel
11/24/2019, 9:13 PMnfrankel
11/24/2019, 9:13 PMs1m0nw1
11/25/2019, 6:19 AMs1m0nw1
11/25/2019, 6:22 AMnfrankel
11/25/2019, 7:05 AMperformance is mentioned as a concernitās not a concern itās a red stop sign
Weāve not been experiencing the issues you are mentioningif youāre using it as a toy experiment, nearly anything works in nearly every context - scala, clojure, etc. but this is like advocating for microservices, monorepo or whatever hype and fancy trend is raging nowadays faas definitely has use-cases but is not compatible with jvm either for price reason or performance reasons if you stand by your reasoning, you should detail your costs and measure performances compared to other no-jvm alternatives e.g. javascript and write about it perhaps youāll also realise it could be improved nothing prevents you from transpiling kotlin to js and using the latter
s1m0nw1
11/25/2019, 7:18 AMbut is not compatible with jvmCan you prove that? Or is that just your strong opinion?
nfrankel
11/25/2019, 7:53 AMnfrankel
11/25/2019, 7:54 AMnfrankel
11/25/2019, 7:55 AMnfrankel
11/25/2019, 7:59 AMnfrankel
11/25/2019, 7:59 AMnfrankel
11/25/2019, 8:53 AMnfrankel
11/25/2019, 8:53 AMnfrankel
11/25/2019, 8:54 AMThe first request made to a Java web application is often substantially slower than the average response time during the lifetime of the process
nfrankel
11/25/2019, 8:54 AMāCold startā in the serverless world means that serverless application is started and initialized to handle the request. In here, āserverless applicationā term represents both application and container itself where user code runs. As you guess, this initialization adds extra latency to the execution of the request since they need to be done before handling the request.
s1m0nw1
11/25/2019, 9:10 AMnfrankel
11/25/2019, 9:22 AMCold starts are a real challenge but you can still get around ityes, if you pay the cost to keep it warm or donāt need faas in the first place
hhariri
nfrankel
11/25/2019, 11:28 AMhhariri