5 Questions to Help You Choose the best Tech Stack
4 min. read
When building something new, it's important to figure out what the Minimum Viable Product (MVP) will be to get your idea into the hands of your customers as soon as possible. Once you have determined the MVP, this allows engineers to have the foundation to begin building as you want to scale. That being said, before engineers begin writing code, you need to choose your tech stack. For a technical or non-technical person it may be hard to choose what you should use to build your product especially with different languages and frameworks that are out here. This post will talk about the 4 questions to ask yourself before deciding the best tech stack.
How big is your project?
If your project is pretty small scale, like a blog or publication, you may need to just use some sort of Content Management System (CMS) to get your idea out there.
If you're trying to build an e-commerce site or something mid-scale, you may need to use more tools and frameworks that combine different integrations to build your project but both the client side and server side don't need to be the most robust.
Lastly, if you're trying to build a large scale project like a social network, or a web application you may need to use even more different languages and frameworks from the database layer all the way to the front-end.
How quickly do you want to launch?
This doesn't have to be an answer that is definite timeline but you should have a rough timeline. The tech stack that you choose to use will impact how quickly or slowly it may take to develop. Once you've decided how quickly you want to launch ask yourself:
- Do you know people who can build on that tech stack?
- Does your tech stack allow for third party integrations?
- Do any similar solutions already exist?
How fast do you want to scale?
You should pick a tech stack that gives you room for future growth. Are you going to need multiple servers because of an increase in traffic? Are you going to need multiple processors? Understanding how much room you have to grow so that you can be ready when the time comes is key.
What type of product is it?
Are you building a mobile app? progressive web app? software as a service? Narrowing this down will allow you to narrow in your search for the best tech stack.
What do you need for an MVP?
I'm sure you all have a dream of what you what you want the product to be but look to see if there's a way that you can test and validate that your idea is worth spending time working on it and building it out the way you envision it being?
Do your research and figure out the tools and frameworks that will solve your solution efficiently in the most cost-effective way that will get your work out there as soon as you can. Hopefully these tips will help you get started.