As with blockchain, there are more vendors and PR people trying to make "no-code" a thing than there are actual users or practitioners.

Until that ratio shifts I'm skeptical.

Java isn't an ideal fit for containerization or horizontal scaling by nature, but if you're stuck with it and really want to avoid using anything other than Java ecosystem tooling, this seems like a timesaver.

Why would Java not be an ideal fit for containerization (why would any runtime not be)? Also, given you don't have to pack everything into one VM (can have many nodes, VMs, load balanced, whatever)...what makes Java particularly bad for horizontal scaling?

Yea I don't understand the original comment... however it is true Java isn't (or at least wasn't until recently) ideal for containerization, since the JVM would not obey things like cgroup limits for memory and CPU. This was fixed in Java 9 and backported to the Java 8 (update 131) however there are still potential issues regarding CPU isolation that are not trivially solved without some explicit configuration.

For a good overview, see: https://mesosphere.com/blog/java-container/

I've backed the KS, used it every day at work for more than a year, never going back to another git porcelain.