Lowdb VS node-telegram-bot-api

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.

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

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.

You have installed lowdb, a tiny local JSON database for small NodeJS projects. This package stores data as an object and supports two operations: read and write. The server app will use express to register, read and update user objects/entries and nanoid to create user tokens.

Maybe you could take this project as a reference? It is a chrome extension built by Vue3 & Vite2. It aksi combines lowdb with chrome.storage to store the notes.

JSON Server works based on Low DB a "Tiny local JSON database for small projects". So you need to configure a db.json file that will serve the data.

So it's a wrapper around lowdb. I'm curious, what benefits does it provide over just using lowdb? And why use lowdb?

you can use lowdb for database system. It is simple and easy. lowdb link npm

Of course, it's good to write API requests yourself. It reduces the dependency on third-party libraries and allows you to control the behavior of the code more. But when there are more such methods than twenty, it already increases the size of the code. It becomes difficult to manage all the logic. This is where third-party libraries(frameworks) come to the rescue. After choosing a language, you can consider the options of different libraries from the list here, on the official Telegram page. For JavaScript I recommend using node-telegram-bot-api and telegraf. For Python you can take pyTelegramBotAPI and aiogram(highly recommended).

We checked if our text is equal to our command and responded with message. It is all main logic from this package, more sendMessage methods or params you can see here. Also we used reply_markup option in which we can use our keyboard, which will be sent with our message. And then we can check if text equal to "en" we will change our language to english and response with message. In addition, if you have a question like can you send message without getting message from user - you can do it. All that you need is to save your user to database like MongoDB with chatId field and use something like express to make CRUD methods to send your message. Here is my example of this 'bot mailer':

The node package we're working with, [node-telegram-bot-api](https://github.com/yagop/node-telegram-bot-api/blob/master/doc/tutorials.md), comes with great documentation. Let's start with one of the methods from the README. We'll tell our bot to send an introduction anytime a user runs /start.

Github repo for more examples and ideas