2
5 Comments

What's your tech stack?

Hey guys,

I'm wondering, as an IndieHacker, what's your tech stack - programming language, framework, no-code platform?

For example, mine is: Ruby and Ruby on Rails.. I have some JavaScript, of course, but I'm definitely avoiding it as much as possible. I have one service/back-engine written in Elixir(Phoenix) and nothing else. I know that it's not the hottest framework, but it's very stable and provides more or less everything one could want for web-development. And, it's constantly improving.

Please share your use-case stack in the comments and vote here (it's a multi-choice poll)

Cheers!

on November 25, 2022
  1. 2

    Pretty straight forward stack of serverless python functions on aws lambda with aws aurora postgres for the backend/APIs. React for the front end. Huge fan of seed.run for CI/CD pipeline

    1. 1

      Nice. I'm wondering; have you tried a non-serverless environment before? It'd be great if you could compare them.

      1. 2

        Yeah, I have a bit of experience across serverless/non-serverless environments. In my experience, and granted this depends on the nuances of the problem you're trying to solve, one of the biggest comparison between serverless & non-serverless stacks would be the time to value serverless stack is significantly faster.

        A serverless environment minimizes the time time to set up, scale and in-depth infrastructure knowledge needed where you can deliver value quickly. I do want to call out that a serverless solution while great for this time to market (amongst other things, it doesn't always make the best long term solution, but that's a larger topic for another thread.

        1. 1

          to me, one big advantage is to non-serverless is that you get full-control of your machine and also - speed. You app will be faster by default.

          1. 2

            I think there's a lot of different cases out there where non-serverless or serverless would come out on top. Not just in speed, but cost, flexibility, scale, time to market, etc.

            Personally, I wouldn't blanket say that non-serverless/serverless is faster or slower. It's all about using the right took for the job.