Twit Alternatives
Similar projects and alternatives to twit
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
ens
Discontinued Implementations for ENS core functionality: The registry, registrars, and public resolvers.
-
nostr
a truly censorship-resistant alternative to Twitter that has a chance of working
-
-
fedbox
Reference implementation of an ActivityPub service using go-ap packages (mirror repository)
-
multihash-serialise
Haskell libraries for interacting with IPFS (by monadic-xyz)
twit reviews and mentions
-
Mastodon.technology Is Shutting Down
Which processes up to 8k requests at a time, waiting up to 10 ms for a batch.
Similar techniques should work on read batching, but I haven't tried that. You can also speed that up some more with the COPY protocol, but IIRC you need to be more careful about escaping/SQL injection.
On my 6 year old mid-range desktop (this CPU[1] and this disk[2]) this program can process ~30k `create`s per second. For about $1500, I could buy a new computer with a Ryzen 9 7950 with 4x the core count/8x the thread count and 2x the single-threaded performance, so around ~10x more processing power, 128 GB of RAM, and a Samsung 980 Pro SSD, which can do 1M Write IOPS (25x more than my SSD) or 5GB/s sequential writes (10x more). So a $1500 computer with a single disk should be able to do around 300k/s. PCIe gen 5 is now coming out, which will allow for another doubling of disk performance.
128GB of RAM means you can keep at least 100M rows worth of index in memory. It's not that expensive (under $10k) to build a server with 1TB of RAM.
Totally feasible for a hobbyist to do without tons of tricky optimization; people spend $20k on a jetski or $80k on a truck. Like I said, the most expensive part is going to be the storage, but you could do something like only store the most recent 1000 tweets per person, and charge $10 to bump that up to the most recent 10 million tweets or something. You'd come out at a substantial profit with that model if you got a few thousand takers. Similarly you could charge to let someone follow more than a few thousand people so you could pay for a read replica or two.
[0] https://github.com/ndriscoll/twit/commit/19b245677b978b42a6f...
[1] https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-6600K...
[2] https://www.disctech.com/SanDisk-SDSSDHP-256G-256GB-SATA-SSD
Stats
The primary programming language of twit is Scala.