operations
mvsqlite
Our great sponsors
| operations | mvsqlite | |
|---|---|---|
| 12 | 26 | |
| 98 | 1,318 | |
| - | - | |
| 5.0 | 0.0 | |
| 19 days ago | 11 days ago | |
| Rust | ||
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
operations
- Use Preferred Tile.openstreetmap.org URL
- Upcoming downtime on 2023-01-22: WILL NOT allow edits [...] may be unable to login to services which requires openstreetmap.org authentication
-
I made a wiki for comprehensible input resources
I see. It looks like this MediaWiki bug for the mobile site: https://phabricator.wikimedia.org/T274807. I'll try to figure out how to get that fixed.
- Show HN: Query SQLite files stored in S3
-
Is it possible to send area to the backward.
It is strange to me that the pedestrian area gets rendered above the building... would you like to create a topic about this at community.openstreetmap.org ? I think this should be handled differently. I guess the next instance then would be to open an issue at https://github.com/gravitystorm/openstreetmap-carto (probably but I'm not 100% sure) or maybe here https://github.com/openstreetmap/operations
- Host your own OpenStreetMap Map Tiles
-
Tile status info and rerender requests not working anymore.
It was a deliberate decision to disable it for the CDN, on the grounds that with multiple render servers and load balancing, it doesn't do what users would expect anymore, see: https://github.com/openstreetmap/operations/issues/681
- OpenStreetMap looking for more US rendering capacity
- OpenStreetMap: Increase US Rendering Capacity
- Servers
mvsqlite
-
FoundationDB: A Distributed Key-Value Store
I’ve been using FDB for toy projects for a while. It’s truly rock solid. That being said, I wish there were more layers.
Ideally someone could implement the firestore or dynamodb api on top.
https://github.com/losfair/mvsqlite
-
Go bindings to SQLite using Wazero
For the rough plan, it's Cloud Backed SQLite meets FoundationDB.
-
SQLite-based databases on the Postgres protocol? Yes we can
- Oh, and if you're wondering about backup to S3, they have that too: https://github.com/libsql/bottomless
- Uh, sqld can integrated with this https://github.com/losfair/mvsqlite, so now your SQLite is backed by FoundationDB!?
- Meanwhile Litestream exists https://github.com/benbjohnson/litestream/
- We Built Fly Postgres
-
Litestream doesn't do SQLite replication anymore (LiteFS does)
Shameless plug of my [mvSQLite](https://github.com/losfair/mvsqlite) project here! It's basically another distributed SQLite, but with support for everything expected from a proper distributed database: synchronous replication, strictly serializable transactions, + scalable reads and writes w/ multiple concurrent writers.
-
SQLite: QEMU All over Again?
This project looks really exciting!
I'm working on mvsqlite [1], a distributed SQLite based on FoundationDB. When doing the VFS integration I have always wanted to patch SQLite itself, but didn't because of uncertainty around correctness of the patched version...
A few features on my wishlist:
1. Asynchronous I/O. mvsqlite is currently doing its own prefetch prediction that is not very accurate. I assume higher layers in SQLite have more information that can help with better prediction.
2. Custom page allocator. SQLite internally uses a linked list to manage database pages - this causes contention on any two transactions that both allocate or free pages.
3. Random ROWID, without the `max(int64)` row trick. Sequentially increasing ROWIDs is a primary source of contention, and causes significant INSERT slowdown in my benchmark [2].
[1] https://github.com/losfair/mvsqlite
[2] https://univalence.me/posts/mvsqlite-bench-20220930
- Show HN: mvSQLite v0.2
- mvsqlite: Distributed SQLite built on FoundationDB
-
Show HN: Query SQLite files stored in S3
That DynamoDB VFS looks cool! I agree that the VFS api makes one think about plenty of crazy ideas. Someone is working on a VFS based on Foundation DB[0] that looks very promising. It was recently discussed here[1]
[0]: https://github.com/losfair/mvsqlite
[1]: https://news.ycombinator.com/item?id=32269287
- GitHub - losfair/mvsqlite: Distributed, MVCC SQLite that runs on FoundationDB.
What are some alternatives?
planetiler - Flexible tool to build planet-scale vector tilesets from OpenStreetMap data fast
awesome-sqlite - A curated list of awesome things related to SQLite
openmaptiles-tools - Tools to turn the schema into other formats
dqlite - Embeddable, replicated and fault-tolerant SQL engine.
kvtiles - Self hosted maps, PMTiles, MBTiles key value storage and server
litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines
mbtiles-php - PHP backend for reading tiles from mbtiles databases
rqlite - The lightweight, distributed relational database built on SQLite.
s3sqlite - Query SQLite files in S3 using s3fs
datasette-stripe - A web SQL interface to your Stripe account using Datasette.
verneuil - Verneuil is a VFS extension for SQLite that asynchronously replicates databases to S3-compatible blob stores.
blueboat - All-in-one, multi-tenant serverless JavaScript runtime.