Macchiato: ClojureScript on the Server

Re:Macchiato: ClojureScript on the Server by bmh100 on Saturday December 03, 2016 @04:05PM (#13097488)

Assuming a commercial web application, appropriately sized hardware, and correctly optimized code, when is "footprint" a significant disadvantage? How is "footprint" defined? When are startup times a significant disadvantage?

[ Parent | on HN ]

Re:Macchiato: ClojureScript on the Server by ledgerdev on Saturday December 03, 2016 @11:57PM (#13098846)

Here's a couple significant disadvantages to the jvm.

A simple jvm clojure app running jetting deployed as an uberjar takes about 12 seconds to start on a 1GB digital ocean vm.

Using jvm clojure as with aws lambda, it takes ~20 seconds for a cold start. Normal java is typically a couple of seconds, and it's likely that a cljs/node instance will be sub-second cold start.

[ Parent | on HN ]

Re:Macchiato: ClojureScript on the Server by dskrvk on Sunday December 04, 2016 @11:12PM (#13103316)

Note that with Lambda a cold start doesn't have to happen every time - if the function is executed frequently enough, the application will be kept around on the executing node.

Also, if your application has fairly stable load, then startup times are irrelevant 99% of the time, since you can just run persistent servers.

[ Parent | on HN ]

Re:Macchiato: ClojureScript on the Server by auvrw on Saturday December 03, 2016 @09:38PM (#13098540)

here, footprint is 'memory footprint,' the amount of main memory used by the application.

this is useful b/c VPSes are priced mostly based on memory

-----

i like that this says it's mostly trying to be "ring for node" ..

[ Parent | on HN ]

Re:Macchiato: ClojureScript on the Server by macco on Saturday December 03, 2016 @05:18PM (#13097773)

If you use Rasberry Pi, real-time web apps.

In most use cases the jvm will be superior.

[ Parent | on HN ]