[nderjung]

Thanks and, yes it does!

We have a whole section in our documentation's guides section on example usecases with database:

https://docs.kraft.cloud/guides/#databases

They work exactly as you suggest, they scale-to-zero when no requests are made and data can be safely stored/transactioned in persistent volumes on the platform too.

[irke882]

Wow, you are responding to a poster who coincidentally has the same name as your main investor. Truly an amazing coincidence.

https://twitter.com/frbergen

Both the twitter above and the HN user posted the link to findtime.fberge.com

Note everyone it's probably a big coincidence! These two posters most likely do not know each other. This exchange is totally legit.

[anentropic]

If this applies to the dbs too then it's quite unusual and worth shouting about, I'm not aware of other providers which offer that!

Looking at https://docs.kraft.cloud/guides/mariadb/ with the Docker stuff in there I'd half assumed maybe DB instances worked differently from unikernel instances or something

Also because of this other comment:

> Because KraftCloud leverages Unikraft, a unikernel library OS project, we are single-process. Postgres is multi-process since it uses the fork() syscall. If you require Postgres, we can set it up for you as a managed service

[fhuici]

Hi, Felipe from Unikraft here. Yes, it applies to DB instances too (all instances are the same on KraftCloud with respect to this).

Regarding multi-process, at present Unikraft has partial multi-process support: some multi-process apps work, others not yet -- we're hard at work completing this support.