48 karma · joined September 29, 2010
hi.kanily at g mail
What i have working as of now: - submit a video and get a snapshot of which stocks were mentioned, sentiment (buy/sell), price delta and reasoning. - analyze a channel and get a performance 'report card' of that channel
I host a multiplayer game on fly. The way I've designed it is, each game server has it's own sqlite database. And each fly server can host multiple game servers, to keep a high utilization. I currently use Litestream to replicate each database to s3 for disaster recovery. I am planning to move from S3 to sftp to save on the high post/put costs that s3 incurs (the actual storage costs are negligible).
I thought what I am doing would be more common place. But it seems that running single machine instances that can recover after a crash is not common after all (or atleast the tooling does not focus on that). Most use cases seem to be serving high availability or scalability.
In the unnecessary (IMO) desire to make everything highly available, I think simpler solutions have been over looked. I can't help but feel that if you need LiteFS, it is possible that you should be looking at a server oriented database like Postgres or Mysql. In that respect, I feel Litestream is underrated and deserves more attention. It serves a use case which is perhaps more in-line with an in-process DB :)
PS. this thread has some really interesting tools though (Marmot, mycelite). Great to see so many options.
Actually, it is possible, but doing a search on a particular segment of rows is a very slow operation - say text search for all employees with name matching 'x', in organization id 'y'.
It is not able to utilise the index on organization id in this case, and it results in a full scan.
Based on a cursory search, these bans are not so uncommon, and it is just scary
[1] https://news.ycombinator.com/item?id=24965432
[2] https://news.ycombinator.com/item?id=24791357
[3] https://news.ycombinator.com/item?id=23057365
[4] https://support.google.com/accounts/thread/5016170?hl=en
(edit for formatting)
edit: looks pretty neat on the UI