Made a little architecture diagram for Micro.blog that reflects the recent server upgrades. A couple simplifications but it’s pretty close to how things work.

Made a little architecture diagram for Micro.blog that reflects the recent server upgrades. A couple simplifications but it’s pretty close to how things work.
@manton Neat! So, the balancer decides if you are trying to publish or consume? And depending on that it sends the request to the Ruby App or the Static servers?
@manton What % of resource utilisation are you getting out of those App instances? Is Ruby that memory hungry?
@paulgrav I don't really need that much memory and would rather have smaller servers but more of them. I glossed over that they are both web servers and also handle the background tasks plus running Hugo.
@manton I know you’ve probably mentioned before, but is micro.blog’s “Ruby” Rails, Sinatra or some other framework, or essentially all custom Ruby code (e.g., your own “framework”)?