I was curious to try out the current Akkaserverless Beta.
After using it shortly (great interactive tutorial btw), I have some questions regarding the adoption of Akkaseverless in a real environment and its scaling, deployment and billingwise in general.
Having deployed 7 very simple services (none of them doing anything at all) the Akkaserverless console shows me usage “statistics” of 10GB of memory used and ~20-25%CPU burning. This is now running for about 10 hours, so I assume it has converged to stable numbers.
I’m not sure if those are real numbers, but how would that scale in the long term? What cost model do I have to anticipate for if I don’t use a service at all in times when we can “scale to zero” which is mostly relevant in billing terms.
To compare resource wise, I have running monoliths with 300 KLOC, running hundred of users, hundreds of services using 1/4 of that memory used and 1/2 of baseline CPU usage of the above during a normal business day.
For sure, that monolith would not scale once load increases significanlty, but, how would one justify this amount of resources being used and billed, for 7 services doing nothing, while building a general purpose application?