3 ms·
The setup I'm using right probably can't be picked by "anyone" but I think is the best/future-proof for small apps and it's also very easy to maintain if you ar
by csomar 7y ago
The setup I'm using right probably can't be picked by "anyone" but I think is the best/future-proof for small apps and it's also very easy to maintain if you are growing.
- Front-End: Vue.js with Bulma.css - Webpack/Gulp for building JavaScript/SCSS. (I have the blueprint here: https://github.com/omarabid/front-root https://github.com/omarabid/front-root but there is still no docs and rough edges). The website is/will always be static files generated by Gulp. First frontier for scaling is eased.
- API: I use a GraphQl server. This avoid the mess that is RESTful. It also give me a nice explorer, so I can make my application and be able to roughly work with it before I have an interface ready. This part is also easy to scale.
- Application: Rust. Technically, you can use anything here. But since I don't have any web components (the site is static and the API is served through GraphQl) then I use Rust which I find very productive. Rust generates a compiled program which run inside a container and makes deployment more enjoyable.
- Database: Postgres/Redis.
- Deployment: Everything runs in a container. I use Hashicorp software for deploying and orchestrating the servers. Terraform if I have a simple single server app. Or Consul/Nomad/Vault if I'm running multiple servers.
It might sound complicated but beyond the initial investment to set things up, you have a stable/reliable micro-services app.