Live data from Hacker News

The appeal of serving your web pages with a single process

utcc.utoronto.ca

61–63 of 63 posts

Re: The appeal of serving your web pages with a single process

#61
post #28

what was that superfast web server, opensource of some sort, from about 25 years ago, single process, single thread? it just raced around a loop taking care of many queued i/o streams

Perhaps it's quark? https://tools.suckless.org/quark/

yes that was it, thx!

Re: The appeal of serving your web pages with a single process

#62
post #5
post #2

and no race conditions whatsoever

Well, unless you're using threads. Or did I miss the sarcasm?

no sarcasm, the code won't have race conditions and sometimes it's great

I actually recently planned to write a single threaded API to free myself from thinking about race conditions

Re: The appeal of serving your web pages with a single process

#63
post #37

I do this for my personal projects. Rust. Axum. Single compiled binary. Even html/js/css is baked into it via RustEmbed. Sqlite + litestream to S2. Cloudflare in front. Works extremely well.

Do you have a link to such a complete app? Would love to take a look and learn.

No, sorry, they are not open source. But they are also not that hard to build. But as far as I know there is no ready solution to build all the boilerplate for you.
Post reply on HN