2
6 Comments

Backend Stack Ecosystem - a Poll for you ...

When you start a new project, what does your backend stack look like?

Preferred language?
What DB?
REST or GQL?

  1. 2

    My latest project is full-on AWS orchestrated with Serverless (https://www.serverless.com/). Cognito, API Gateway, Lambdas, SQS, SNS, DynamoDB. Bit of a brick wall learning curve at first, but now that I'm past that, it is going shockingly smoothly.

    Node for lambda language, httpapi / REST on the Api Gateway.

    Very likely to use it again, with one possible change - perhaps using Auth0 or something else for the authentication. Cognito is far and away the weakest part of that stack.

  2. 1
    • Node
    • DynamoDB, Firestore
    • Rest / Cloud functions

    I used to use the Serverless stack a lot and I've found it to be really nice for a small team but a lot of our new projects are build on firebase.

    All have pros and cons but I've found Firebase the fastest to move and adapt along the way.

  3. 1

    Python / Django + Graphene, Graphql. For database: PostgreSQL from the get-go. Redis sometimes when I am using distributed workers (Celery).

  4. 1
    • ClojureScript on Node
    • JSON files until I need Postgres
    • No REST or GQL - just endpoints that read/write exactly what the client needs.
    • I run a bunch of sites ("small bets" or experiments) on a $10/m Digital Ocean box using Piku.
  5. 1

    Node or Go, PostgreSQL, REST.

    That said — don't listen to what anyone here says. Use the stack in which you're most comfortable and productive.

  6. 1

    Java (Spring Boot)
    Aurora / ES
    REST

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 47 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 27 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments How I Launched FrontendEase 13 comments