9
9 Comments

What architecture to choose for a small SaaS?

Hi all!
(English is not my native language, I apologize in advance for any mistakes)

I'm backend dev on Node.js, and I build my first product on the SaaS model.
I have some experience developing on AngularJS/2+, but I'm still bad in frontend.

And the main question "What architecture to choose?"

I thought over Node.js for backend (because I know him well enough and several more API services will be launched there) + Vue.js on UI side (will try yourself in something new), with REST interface.

But maybe better will choose Monolithic architecture?
Smth like Next.js/Nest.js.

I already have near 6 end-points on Node.js side, but I thought that maybe I should switch to a monolithic architecture in advance before the application's functionality went too far.

Thanks for your answers!

What architecture to choose?
  1. Save REST
  2. Monolithic
  3. Other (write in comments)
Vote
  1. 10

    Stay mono at the early stages will save you time. Going REST, Microservices, GraphQL at this point will slow you down. Ship fast and early. Get it built and use the traction you get to help you decided what to do next.

  2. 3

    If you want to go fast and are the only developer go for a monolith. It will serve you well for a long time. If you make it a very modular monolith breaking it up into smaller services will be less of a problem if it ever comes to that.

    A monolith will take you a lot further than today's "wisdom" says it will. You are not Google, Facebook, Netflix or Microsoft with hundreds or thousands of developers. You are one guy and you need something that will enable you to go fast.

  3. 2

    The answer depends on what kind of SaaS you are building and what you are comfortable with imo. If, for instance, your SaaS is doing compute heavy stuff, I'd go for a micro services approach whereas there are many other cases where the extra architecture will slow you down in the beginning (unless you are a Docker and Kubernetes ninja).

  4. 2

    Architecture should serve your needs. You didn't say what you are building, therefore no advise can be given.

  5. 2

    Whatever you know best. The quality of your work will speak more than the quality of the tools you use. "You wouldn't ask a fish to climb a tree".

  6. 2

    Definitely a monolith until your have a pressing need to break it up. It doesn't hurt to have a game plan for doing so, but I'd really just think one order of magnitude ahead of where you are. I.e. worry about how to handle 10x your current traffic but don't worry about 100x or 1000x.

    If I only knew JavaScript, Redwood.js would be my first choice. It's the closest thing I know of to a Rails-like experience for 2020 JS I know of.

  7. 1

    Front End (Vuejs 2.x) Single page application
    If you know Angular 1, then Vue is quite easy.
    You don't need Nuxt as you can just upload your files to a static host without any servers
    For Backend, i suggest all Cloud Functions (use Vercel or aws lambda functions)
    Database - Mongodb Atlas.

    Thats it, thats your multimillion dollar minimal stack right there.

    1. 3

      Thanks!
      But I already use PostgreSQL :)

      your multimillion dollar minimal stack - I will strive ;)

      1. 1

        Goodluck, yeah postgres is fine too as long as its hosted.

  8. 2

    This comment was deleted 3 years ago.

  9. 2

    This comment was deleted a year ago.

Trending on Indie Hackers
After 10M+ Views, 13k+ Upvotes: The Reddit Strategy That Worked for Me! 42 comments Getting first 908 Paid Signups by Spending $353 ONLY. 24 comments I talked to 8 SaaS founders, these are the most common SaaS tools they use 20 comments What are your cold outreach conversion rates? Top 3 Metrics And Benchmarks To Track 19 comments Hero Section Copywriting Framework that Converts 3x 12 comments Join our AI video tool demo, get a cool video back! 12 comments