5 ms·
For a web-app of some sort? Host: VPS on OVH Database: Postgresql Web layer (server-side): Grails Web layer (client-side): Javascript - probably vanilla, ma
by mindcrime 4y ago
For a web-app of some sort?
Host: VPS on OVH
Database: Postgresql
Web layer (server-side): Grails
Web layer (client-side): Javascript - probably vanilla, maybe React. Bootstrap.
Auth / SSO: Apereo CAS
Deployment automation: Ansible
CI/CD - Jenkins
Issue tracking: Bugzilla
IDE: Eclipse
DNS: Route 53
If I felt the need for dedicated micro-services for the backend, I'd use Java and Spring Boot.
If needed, possibly Apache HTTPD as a reverse proxy.
For a lot of stuff that might fall under "other", like sending email, or text messaging, yadda yadda, I'd use Amazon services: SES, SNS, etc.
For an MVP I'm not sure if I'd even bother building Docker images or not. But if/when I had to scale up, then I'd definitely package as images and deploy using Docker or K8S. At some point if the thing got traction and needed to scale Big Time™ then I'd probably go to Amazon EKS or Azure AKS.
If I needed a mobile app... well, I'm not really a mobile developer, but I've been picking at learning Flutter. So probably would continue with that.