remake-framework VS Lowdb

Remake is an open-source framework that can do in 1 line of HTML what takes other frameworks 100 lines of code.

* Form submissions

All of this is pretty trivial to get working out-of-the-box with very little effort from a dev. So no one has to reinvent the wheel.

And these features, if done well, are all that 90% of businesses need to create value for this customers and become profitable.

I'm really excited about this space. My email is in my profile if anyone wants to talk about it further.

[0] https://remaketheweb.com/

Mavo is great, but doesn't come with a backend. I'd recommend checking out Remake as well (https://remaketheweb.com/), which comes with a backend and user accounts out of the box — and has a really simple syntax. It's made for beginners (who only know HTML & CSS) who want to build their first web app and get an idea of how everything fits together.

There are a lot of great options, but it depends on what you're trying to do. If you're building mobile apps, Adalo or Glide, but if you're building web apps, then Bubble or Remake.

Remake sweeps away those excuses. I took a few hours on a Friday to sketch out an idea for Shelf.page and build it with Remake. A preview of the shelf.page web app Shelf.page is representative of a really common kind of app. Every user gets a profile or account page at a unique URL, with a bunch of fields to customize their page and edit it themselves.

You could contribute to https://github.com/remake/remake-framework, which me and several other devs have been working on for a couple years.

https://github.com/typicode/lowdb is a cool option.

I just finished the first stable version of go-store, a lightweight embeeded database written in pure Go. It was heavily inspired by lowdb. The motivation was that I needed something simple to store information for another project and that I wanted to try out Go's generics.

https://jsondb.io/ or https://github.com/typicode/lowdb

By default, requests are stored locally in a JSON file with the help of LowDB.

For 1: Don't.* For 2: You're looking for a cache. I've published an OS npm module. Looking at the code might help: https://github.com/tq-bit/qache/blob/master/src/Cache.ts For 3: Maybe the code of lowdb can point you in the right direction: https://github.com/typicode/lowdb/tree/main/src

Another thing you might consider is literally using the filesystem as a database. There are plenty of vanillla ways to simply read/write to JSON or you could even use a JSON based db github.com/typicode/lowdb again you don't need to think about it as a db your just handling JS objects.

I did want something performant so that I would (hopefully) not run into issues when there are around 100-ish clients connected at the same time. I looked at low-db for a while but did not like that it would JSON.stringify my whole database on every change, which could become a problem when it becomes to big.