Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to a more performant hoster #3

Open
arjpar opened this issue Apr 22, 2024 · 1 comment
Open

Switch to a more performant hoster #3

arjpar opened this issue Apr 22, 2024 · 1 comment

Comments

@arjpar
Copy link

arjpar commented Apr 22, 2024

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.

@arjpar
Copy link
Author

arjpar commented Apr 30, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant