Andreas

Posted on Dec 27, 2019

What is your preferred Tech Stack?

#discuss #question #webdev #watercooler

I'm wondering which Tech Stack you prefer especially for your web development projects. What are the advantages of your favorite stack?

Top comments (32)

Vince Ramces Oliveros • Dec 28 '19

None. You'd never stick to one stack to solve a particular problem. Clients, Employers and hipsters prefer new technologies. That's why I couldn't stick to one tech stack, but a more robust tech that others couldn't compete with.

Dĵ ΝιΓΞΗΛψΚ • Dec 28 '19

my goto stack right now is:

frontend: svelte + tailwind css
backend: .net core web-api
db: mongodb

i choose this stack because it's the best balance between:

ease of development
ease of maintainability
efficiency of resulting code
cross platform deployment

for those interested, i've developed a c# dotnet new template project for quickly scaffolding a web-api project for mongodb.

Patryk • Dec 28 '19

GitLab
Docker{,-compose}
Postgres or PostGIS (I occasionally add other DBs)
Django for back-end
Vue.js for front-end
Seeing as I can't design, Quasar framework for Vue
Have worked with Graphene (GraphQL) and DRF (Rest)... I think I like Graphene better (single api endpoint, query without {under,over}fetching), but both are very pleasant to work with
Pytest, Cypress, Jest for testing

I think GitLab-CI is wonderful to automate building containers, running tests, and deploying. GitLab's issues give you nice boards, so I open issues for things I am working on (e.g. add Login component), give it the appropriate labels (front-end, in process, high priority), and move it around Kanban boards.

Docker makes setting up dev environments very easy. Even though many people disagree, I love running DBs in docker. Then I can easily add postgres, postgis, redis, mongo, elasticsearch, etc. to any project. Once the containers are built, I can just click a "deploy" button, and I have a simple script that stops my project, and brings it up with the latest version.

I am a big fan of using RDBMS for anything that manages user accounts. Postgres and Django support JSON fields, so I can easily add NoSQL features to it. I am currently planning to add ElasticSearch to my website, but that will still be added after PG, and not a replacement.

PUT/UPDATE
  -> let Django handle connection
    -> save model
      -> in post save handler, queue Celery task
        -> make Celery serialize object and upsert into ElasticSearch

Django because Python is beautiful, Django does everything you need, meaning fast to start with, no reinventing the wheel, but you can easily extend it.

Vue.js because it uses ES6, and no ugly JSX (personal preference - if you read this and like JSX, don't get offended :)

Pytest, because why would you use anything else?

Lewis kori • Dec 28 '19

This is definitely my favorite stack too vue + django + docker = heaven.
I haven't used graphene in production though. Still stuck on DRF.

Patryk • Dec 29 '19

I've heard that Ariadne is easier to extend than Graphene. Judging by the mess that the multiple inheritance is in Graphene, I am not surprised.

I'll have to give that a try, soon. If you want to implement graphql, I highly recommend you try both.

nalajala4naresh • Jan 1 '20

DB : MongoDB
Backend : python with DRF on docker & AWS ECS
front-end : React

xtrm-co-in • Mar 6 '21

Can you please help me deploy quasar build files to django server ?

Kien • Dec 28 '19 • Edited

Most of my project are enterprise app so I'd prefer

Spring cloud to build Restful API,
Front-end using ReactJS + ReduxJS + Material UI,
gitlab for CI/CD. I dockerized both BE & FE so I could deploy them to a k8s cluster or docker swarm for small project.
I managed infrastructure using terraform.
Sometime when I need to build mobile app, I'd use Flutter + Firebase

Burhanuddin Udaipurwala • Dec 28 '19

Seeing you use React in your frontend, any particular reason that you use Flutter instead of React Native?

Kien • Dec 29 '19

I personally dont like javascript so I'd avoid using it as much as possible. I use it for FE web app 'coz there are no other choice

Marco Colli • Jul 31 '22

Ruby On Rails. It's efficient and it gives you everything you need. I've been developing with it since 2010 for passion, then I launched several successful businesses with it (starting from 2017).

Here's some websites that I have built with Rails, PostgreSQL and minimal frontend (HTML, CSS, JS):

PHP and cigars • Dec 28 '19

Stylus
Grunt
jQuery
MariaDB
PHP with own framework
Elasticsearch
Vagrant VM with Ansible
PHPStorm for IDE.

I would not argue, that the stack is better, than an other tech stack, but i know them well enough to be productive.

Patryk • Dec 29 '19

I would not argue, that the stack is better, than an other tech stack, but i know them well enough to be productive.

Luckily, the question isn't about "the best," but our preferences, so there are no wrong answers :)

Andreas • Dec 30 '19

Exactly! 😊

Matthew Daly • Dec 28 '19

I spent four years at an agency that did mostly Phonegap apps, and at the time my preferred stack was:

Django and Django REST Framework for the API
PostgreSQL and Redis as data stores
Angular 1 for the app

In 2015 another dev joined and given that I was the only dev of three who knew Python, I felt we needed to standardize our back ends so someone else could pick it up if I got hit by a bus, so we decided to go with Laravel for future development since we all knew PHP.

Later, after leaving that place, I switched from Angular to React. I'm currently building an app with the following stack:

Laravel
GraphQL
MariaDB
Redis
React

I'd prefer to use Postgres over MariaDB, but otherwise it's my preferred stack.

Lorenz Kitzmann • Dec 28 '19

Still Ruby on Rails in the back, HTML with just enough JavaScript in the front. Sometimes VueJS if the app requires it.

Grant Watson • Dec 28 '19

My favorite stack right now is React/Node/Firebase. But that is because its what I am currently working with at work. On my next project, on as different stack I may be working with PHP and Laravel and that may become my favorite.