Stack

Choosing the stack to build a project is an intimidating process, especially in JS ecosystem, where we see a new framework almost every week.

Because of that, you will always see the eternal debate about which JS framework is the best. Actually, all the JS frameworks are good for the specific problem that were built to solve.

In Bitsoven, we use a variety of tech stacks like:

• M/PERN: Mango/PostgreSQL, Express, React, NodeJS
• M/PEAN: Mango/PostgreSQL, Express, Angular, NodeJS

Usually we go with NestJS to handle the backend part, and we use the right frontend framework depends on the project needs: React, NextJS, or Angular.

Recently, we start adopting BunJS to replace NodeJS, after we noticed the performance improvement after using BunJS to run the JS projects.

For full stack monolith application, we use AdonisJS, in some situations, or by the client request, we use Django.

What architecture we use?
Generally, we’re not trend followers, for that we choose the project architecture depends on different factors like:

• The complexity of the project.
• The daily active users if the project already exist.
• The scaling plans and the targeted audience.
• Where the project will be deployed and planned infrastructure budget.

Based on these factors and some other we decided what will be the best architecture for the project.

Do we use microservices architecture?
Yes, if the microservices architecture is what the project really needs, we’ll go with it, undoubtedly.

What is our microservices tech stack?
We don’t have a specific tech stack for building the microservices, why?

Simply because we use the best stack for doing the specific task, for example, if one of the nodes is responsible for doing some data cleaning task, we definitely will use Python to get that done. If another node is responsible for dealing with a hardware, here the best stack could be C or Rust, and so forth. For general tasks, we usually go with Golang.

How we do the deployment?
It’s all depends on the specifications of the project and the planned budget for it. We deploy on any cloud provider: AWS, GCP, Azure, or using a VPS on a hosting provider you trust, or we can handle that for you on our own infrastructure.