4 ms·
I like to keep things simple so over time I removed stuff from the things I use and kept the things that has the largest reach. So what I use to prototype is ve
by dkarras 5y ago
I like to keep things simple so over time I removed stuff from the things I use and kept the things that has the largest reach. So what I use to prototype is very similar to what I use to deploy:
* Typescript + Vue on the front end (with nuxt) - NO SSR but nuxt precompiles the pages for me so I don't get the SEO hit. Front end can be served from any CDN basically for free.
* Node for the rest API with a custom, very simple and declarative framework that wraps HTTP, this only replies in JSON (also typescript)
* ArangoDB for all database needs. Has key value store, document store, graph store, so best of all worlds. I can use it like a RDBMS where it matters because graphs support relationships so no data duplication AND no need to normalize.
I can basically do anything with those, from quick prototypes, to a very low traffic website to serving millions (managed k8s, horizontal scaling comes into play then).
- karmakaze 5y ago+1 the choice of Vue for the front-end. I would choose a different backend (Go, Kotlin, F# but that's just me) and PostgreSQL or MySQL. As mentioned: for you probably Python+Django (rendering pages, not an API), if you want/need a dynamic front-end maybe Vue+Firestore (or the like), 3rd choice Vue+Django. From personal experience I can say it's very easy to get 'caught up' in the back-end tech and lose focusing on the front-end/product/customer.