ntfy-android VS bbolt

Maybe try Ntfy, it has great support for automation apps through intents(for reacting) and http requests(for sending). Great documentation too.

I've found the intent in the code (that is linked in the docs):https://github.com/binwiederhier/ntfy-android/blob/main/app/src/main/java/io/heckel/ntfy/msg/BroadcastService.kt

Also, I had recommended AutoRemote/Join since it has a friendly interface and ditect events in Tasker. You could also possibly use Ntfy, but it is not very user friendly and has no direct events/action; you have to custom create http requests/receive intents and other complexities etc(though it's free).

GitHub (Android): https://github.com/binwiederhier/ntfy-android

ntfy - PUT/POST to your phone (version 1.14.0): Send notifications to your phone from any script using PUT/POST requests

Integrate it with the Ntfy notification app that has great HTTP Put/Post support.

https://github.com/binwiederhier/ntfy-android (disclaimer: mine, self-learner too)

Based on this [GitHub document](https://github.com/etcd-io/bbolt) for BBoltDB, we can understand that Go Code be used to create a BBoltDB database on the system. The key-values added & operations done on them in that Go Code are stored in the BBoltDB database.

A Locker is a store on your file system (built on top of the amazing bbolt).

- bbolt for storage on disk. In order to get the smallest db file size possible make sure you insert the keys in order and set:

I'm wanting to store some wasm modules (as []byte) in BoltDB. Right now the modules are <1MB, but eventually, they could be 10-50MB in size. Is this going to reduce the performance of BoltDB all around, if the size of a value is this large? If it makes a difference, I'm using the Storm toolkit for querying.

bbolt - An embedded key/value database for Go.

For learning goroutines and channels, I usually recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt. It's relatively simple and you're more likely to run into common manifestations of concurrency issues running disk operations.

If you would like to explore usage of channels, I highly recommend writing a program that reads from files and writes the data in a dummy database with something like https://github.com/etcd-io/bbolt.

No transactions, no consistency guarantees, no benchmarks, global locks in the storage implementation, a collection is copied in its entirety on every insertion to it...I realize it's not for the same use case as MySQL or MongoDB, but a more obvious comparison here is e.g. https://github.com/etcd-io/bbolt. So why should someone use this over bbolt?

use go-sqlite3 to work with sqlite3 is one choice.

https://github.com/etcd-io/bbolt is another pure go option.

cznic seems like an alternative to bbolt. nice to have some options.