Infrastructure ideas #3737
Replies: 3 comments
-
I have a quick draft ready: How's this? Currently, LinkFree is running on DigitalOcean and is managed by MongoDB, but only one person, Eddie, has access. After an outage this morning, improving the infrastructure and maintenance is essential to minimize the risk of future outages. One idea is to move back to Kubernetes on Civo using Pulumi to manage all the infrastructure. This was started in the infrastructure repo but has yet to be completed. This approach would provide more control and flexibility over the infrastructure. Additionally, implementing an option at the DNS level, such as having a secondary Kubernetes cluster running the main branch of LinkFree, would allow for accessible domain switching in case of an outage. This would minimize downtime and allow the team to focus on resolving the issue without worrying about uptime. Other ideas to improve the infrastructure and maintenance include:
Overall, taking proactive steps such as the above can help minimize the risk of future outages and ensure that the team is prepared to handle them when they occur. |
Beta Was this translation helpful? Give feedback.
-
Please feel free to modify and/or change any of that btw |
Beta Was this translation helpful? Give feedback.
-
As we have moved to Vercel and plan to be there for the foreseeable future, I will close this discussion |
Beta Was this translation helpful? Give feedback.
-
Currently LinkFree is running on Digital Ocean app and managed MongoDB, but only Eddie has access.
Logs have been moved to Logtail where the maintainers can get access.
What ideas would help improve the infrastructure and maintenance?
One idea is to move back to Kubernetes on Civo using Pulumi to managed all the infrastructure, this was started in the
infrastructure
repo but not completed.Beta Was this translation helpful? Give feedback.
All reactions