[billllll]

There's some cool ideas here. From what I understand, you basically implement a few endpoints in a serverless-esque fashion, which have access to methods to store data, and the engine will keep the client updated and handle consistency?

I can definitely see this as something to bootstrap a backend quickly. It could serve as a nice in-between of Firebase/Supabase and a fully fledged server.

It took me a long time to grok the docs though. It would be great if there were more simple examples. The landing page refers to a lot of the nitty-gritty details, including method names and services in the architecture, but imo that's getting into the weeds before explaining the value prop. I also had a hard time figuring out the apidemo page on my phone screen.

[vanishs]

First of all, thank you very much for your feedback.

Yes, as you said, gw and api in Lockval Engine implement stateless services, db implements ACID for front-end and back-end data, and trigger provides calling methods outside the engine.

So this is a complete closed-loop backend engine. It provides the most basic computing and data synchronization capabilities, and other functions can also be provided to upper-level scripts in the form of plug-ins

Sorry for the very lacking and messy documentation, I'll try to get them out of there as soon as I can. I made apidemo and playground pages, I think these two pages can help you understand how Lockval Engine is used in a more intuitive way. In addition, these two pages can be downloaded locally to build the experience yourself.

I'm also sorry that none of these pages are optimized for mobile, web development is really not my strong point.