simple examples for developers to build database on top of engula?

[hongjic]

I'm new to engula and am still learning everything that's happening here.
Generally I very much agree on the goal of engula "to build reliable and cost-effective databases with less effort and more confidence" and the modularized design does look like align with this goal, but I don't see any examples or articles explaining how will the design of engula help developers to build a database with complex data modeling (for example SQL) on top of engula.

It would be great if we can have at least one non-kv example of engula engine and explaining how it benefits from the modularized architecture (how things get reused and what customizations can possibly be achieved). This will definitely broaden peoples' imagination.

A first step could be, in my opinion, to model the data types in Redis(hashes/sortedsets/etc.), since they are both simple and functional, well-known by everybody. If a "Toy Redis Equivalent" can be implemented on top of engula with limited code, the value of engula can be truely proven, what do you think?

[huachaohuang]

Yes, building a Redis compatible database can be a very good example, considering that a lot of people love it and are familiar with it. I think more complicated databases with interesting data models can be built once we provide a decent storage engine. For example, the Luna engine we are working on. However, building a sophisticated storage engine takes time, let alone that we want to make it serverless. So we still have a lot of work to do here.
BTW, I'd rather like to see people building different kinds of databases on Engula, instead of doing it ourselves. So if you have any interesting ideas that can be potentially built on Engula, welcome to share :)

[hongjic]

thanks for reply:)

A redis compatible Database can be a lot of work though, what I’m proposing is just to build a toy example to demonstrate the design and usage of engula. A good analog is Tokio as an asynchronous library, have an example redis server and client build on top of it, to explain the designs and best practices (which can only be best explained by the core working group)

I do understand that at the current stage this may not be a high pri, but really looking forward to see such a thing:)

[huachaohuang]

Yeah, I actually got an issue here to port mini-redis to store data in Engula. Just no one seems got time to do that yet :)

[tisonkun]

@huachaohuang I guess @ZhongliGao and potential others will be interested to give it a try. But the abstraction is under continuous refactoring with a main force to implement the luna engine. To avoid conflict each other, this effort can be revived after abstraction becomes more stable :)