📄️ Concurrency
As Klerk is designed to be simple, concurrency is something you can mostly ignore. However, there are
📄️ Jobs and Actions
When processing commands, Klerk doesn't allow synchronous execution of code that has side effects. In other words: if
📄️ Security
Klerk has some properties that helps you secure the data:
📄️ Persistence
Klerk uses an SQL database under the hood to persist the data. It creates tables prefixed with klerk_. You are free to
📄️ Performance
Klerk is designed so that you can achieve low latencies and high read throughput without
📄️ Java interoperability
You will primarily use Kotlin when developing your application. Since both Kotlin and Java runs
📄️ Data Migration
When your models evolve, you must migrate existing data to be compatible with the new
📄️ Troubleshooting
If you get a gradle problem with the dependency, check if the problem is related