You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I noticed that the page response/load time for Globasa.net (and relevant subdomains) is quite slow. I was wondering if you all would be open to switching to a better hoster?
--
I have a few ideas that would greatly improve the performance & security of the entire suite of sites (globasa, learn, dictionary, etc). But I would need to have an understanding of the general architecture of the site first.
The text was updated successfully, but these errors were encountered:
Hi @ShawnPConroy I'd like to add my thoughts here as Github is a more permanent record of information rather than a service like Discord.
Essentially I would propose to use a microservices serverless-based architecture. A fast static site engine like Zola could be used for the main site (root domain), learn (xwexi), readings (doxo). The learn & readings site could use mdbook as an SSG. The main, learn, & readings can be served through a CDN like Vercel, Netlify, etc. The dictionary API & backend could be written in Gleam, the caching layer could be done in DragonflyDB - it could be hosted on a serverless platform like AWS Lambda. If you all design & implement the system properly it could be able to handle millions of requests. If you have any questions or points of clarification I would be more than happy to answer them here (on GitHub).
Hi, I noticed that the page response/load time for Globasa.net (and relevant subdomains) is quite slow. I was wondering if you all would be open to switching to a better hoster?
--
I have a few ideas that would greatly improve the performance & security of the entire suite of sites (globasa, learn, dictionary, etc). But I would need to have an understanding of the general architecture of the site first.
The text was updated successfully, but these errors were encountered: