Show HN: Lockval Engine – A distributed backend KV engine that can run scripts

> that can simulate the rules of the world in your imagination

What does this mean?

For safety, the script does not provide any API that harms your environment. But you can use the Go plugin to write the API you need and provide it to the script.

The solution can be found in "Use api.*.so for more functionality" in [apidemo](https://apidemo.lockval.com/)

Go plugin code: https://github.com/lockval/api.so

In addition, Lockval Engine includes db and several supporting APIs.

Lockval Engine is developed around the concept of data-oriented programming. Therefore, it is generally not recommended to use an external database.

The db in Lockval Engine is a bit like redis, which provides hot data in memory and saves changing cold data in real time

Regarding the location of db in Lockval Engine, you can view the architecture diagram on this page: https://lockval.com/docs/

Lockval Engine is not yet open source software, and the code and documentation of some peripheral tools are on the github homepage.

I have been thinking about the most suitable business model for Lockval Engine, such as finding suitable funders.

This is not an issue that needs to be considered recently. Lockval Engine still has many things to do, such as improving the documentation, collecting more feedback and stabilizing the API, and so on.

Take the recently popular actor model as an example. Each player is an actor, which can not only ensure the simplicity of development, but also ensure the atomicity of the player's data in one operation. But if a player-to-player transaction system is designed, it is difficult for this actor model to achieve the atomicity of this transaction.

But Lockval Engine can easily do all this. Because Lockval Engine is data-oriented programming. It provides a pair of APIs: GetAndLock and PutAndUnlock. You lock the data when you fetch it, and unlock it when you complete the modification.

And this pair of APIs will also synchronize the modified data to the front end. In this way, you don't need to worry about how to send data to the front end when designing functions. Other frameworks or codes need to complete this function by themselves.

Other advantages include but are not limited to: In this distributed architecture, the atomicity of hot update code and configuration. It won't happen that half the system is an old script and half is a new script.