If only lynxchan used the native postgres in Bun instead of mongodb... Shit would be blazing fast. The effort to implement that would be quite the task though.

what's stopping people from fucking around and using an actual compiled programming language

>>11015 Because it has to be compiled?

>>11039 do you even realize how many bugs compiling can scrape up

This site would be perfect if it had a traditional front-end -_- Since the front-end and back-end are supposed to be separate in LynxChan does that mean I can write my own front-end and have it connect to 8moe backend behind the scenes?

>>11015 got it so like typescript

>>10518 Is there a single non-meme web service that uses meme interpreters like Bun or Deno? I mean it's nice if it's faster, but compatibility is a lot more important than anything else. Extensive testing would be necessary to make sure it supports everything and doesn't introduce vulnerabilities.

>>11779 Twitter/X uses Bun according to the frontpage of bun.sh. It might be a meme but it definitely has a few million users.

>>10518 Bro thinks this MATTERS. If your website is actually bottlenecked by your webserver of all things you're probably coding in fucking Ruby or something. >>10519 That might actually make more of a difference. Making large backend changes without having type checking to see what you forgot to fix is hell though.

>>10519 >>11942 How does using bun's native postgres any different from regular postgres? Isn't mongodb supposed to be a better fit for document type storage than postgres while also scaling better?

>>13006 I don't know about bun's postgres module, but SQL databases are more than capable of handling the load of a site like this. Halfchan runs on MySQL (probably a very old version). You don't actually need super extensive scaling. Most of the workload on the database is ready-heavy operations, which are simple to cache, so requests don't even have to hit your database at all. You can use stuff like memcached, Redis, Varnish (fullchan definitely uses this), etc. I don't think you can leverage the advantages Mongo would offer, while the drawbacks are immediate. I'm pretty sure it doesn't make the site any faster. I'd be more interested in the backend of this site if it used SQL because I personally like SQL and don't like Mongo too much.

>>13306 if you're hitting a socket for cache then you're not in a hurry. a chan seems like a pretty settled idea, there has to be one written in go or something.

databases are gay. use files in tmpfs. chans are meant to be ephemeral.

>>14044 you're not entirely wrong, but you shouldn't underestimate the human ability to make things slow

>>13306 I previously worked on an enterprise project which was basically an API backend for a bunch of video streaming services, including some on the same scale as Netflix. It ran on SQL and Ruby on Rails 3.1, and didn't even have auto-scaling until a customer lost their shit over it when they found out. What made it possible was using redis for every API endpoint. Cache is king.

>>14363 >checking license validity >sending a lot of video files aside from requiring peering for infinite traffic cap, is this supposed to be impressive?

>>14368 There were also favorites, fetching subtitles, keeping track of the last video position, and probably other stuff I've forgotten. Considering the scale of the project and the fact that our Ruby/Rails didn't even have virtual multi-threading active (forked processes instead), I thought it was impressive, and it made it clear to me just how important caching is.

Lynxchan uses mongodb as a "cache", it uses that nomenclature for variables in the code. Yes, writing things to disk in a database is a "cache" now.

>>14373 that's still practically 1 reader 1 writer situation, so nothing technically challenging. classic throwing hardware at engineering mistakes, but everyone got paid so who cares i guess. for example, you're in way more trouble if you want to make a chat with a counter. literally just passing plain text around, no accounts, and merely showing number of connections immediately requires special considerations to not make thing trivially dosable by making a lot of connections die at the same time.