I'm also curious if anyone can speak to the advant...

# kvision

[spierce7]

I'm also curious if anyone can speak to the advantages of using KVision over just react with Kotlin.

[ashmelev]

Hi. I use KVision for full-stack systems. I run the KVision-Spring back-end and the integration simplicity that KVision automates make the development and maintenance of these apps at least 2X faster to develop and greatly eases the communication between front- and back-ends. So, everything is in Kotlin and we do not need to change any of the long-pre-existing Spring-based microservices code built by the rest of the team. We deploy the KVision app as a single container into a Kubernetes environment removing the need for server maintenance, etc and team members can move smoothly from maintaining API-only Kotlin/Spring components to KVision systems. We use Google Jib to build distro-less containers for simplicity of the CI/CD pipe and KVision fits that perfectly.

Basically KVision makes for a seamless and homogeneous, fully containerized environment

[spierce7]

Are you using KVision for server side rendering?

[spierce7]

Nevermind. I think I misunderstood what you were saying.

[Robert Jaros]

Alex refers to KVision fullstack interfaces:
https://kvision.gitbook.io/kvision-guide/6.-full-stack-development-guide/overview

[ashmelev]

Robert is correct. However, we further package the KVision-generated UI code and statically deploy it from the Spring-based KVision back-end (this makes the whole app run from a single container)

[ashmelev]

It's a slight difference and easy to implement with a few lines in the Gradle file