manton
manton

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.

Boxes and arrows showing the different Micro.blog app servers, database servers, and static file servers.
|
Embed
Progress spinner
vincent
vincent

@manton sexy 😍

|
Embed
Progress spinner
miguel@indieweb.social
miguel@indieweb.social

@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?

|
Embed
Progress spinner
paulgrav@mstdn.social
paulgrav@mstdn.social

@manton What % of resource utilisation are you getting out of those App instances? Is Ruby that memory hungry?

|
Embed
Progress spinner
manton
manton

@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.

|
Embed
Progress spinner
numericcitizen
numericcitizen

@manton always cool to get those behind the scenes look!

|
Embed
Progress spinner
matt_garber@mastodon.sdf.org
matt_garber@mastodon.sdf.org

@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”)?

|
Embed
Progress spinner
In reply to
manton
manton

@matt_garber Sinatra.

|
Embed
Progress spinner