A modern programming language that makes developers happier.

kotlinlang

hey everyone. i'm starting up my first kotlin/tornadofx project (coincidentally my first desktop app ever). i've been living in the webapp world for about 5 years now working with java and spring (and various other languages) and have an itch to create an American Football Simulation game (no 3D graphics, just really a bunch of spreadsheets and simulation engines, lol) and this seems like the perfect pair (Kotlin/TornadoFX) for a cross-platform desktop app. My question to you folks is... what's commonplace for the, uh, "backend" i guess you would call it for a desktop app. I've used plenty of RDBMS for webapps (postgres, mysql, sql server, oracle, plus some NoSQLs), but i know that's not how desktop apps work (you don't download madden and also have to install postgres for it to work). do people still use frameworks like spring (spring-data, hibernate, etc) and use an in-memory database? do people just write things out to json/xml/csv/proprietary format files and load them into memory when the app starts up? I'm just curious what you daily tornadofx-ers use for a "backend" to your apps?