So, you are finally building something? I hope you didn't forget the importance of the discovery phase wink - wink, which I covered in my previous post wink - wink. But we are here to discuss the technology stacks and, most importantly, how to make this process cheaper.
I'm sure you have already googled some of them and probably even picked up something for your project. So we'll not pay too much attention to it. By the way, I'm carrying an idea to write about the biggest product companies and the tech stack they use. Something like Forbes 100 and their choice of tech stack. So if you find this idea interesting or helpful, write in the comments, so I know what to write about. Let's get started!
I understand that startups are frequently on a limited budget. That's why, in this post, we'll discuss what factors influence a tech stack's price and find some recommendations on how to save money.
The maturity and popularity of specific technologies greatly influence the price of the technology stack. The old and popular technologies are proven, reliable, and have many specialists to choose from. You can always find developers specializing in Java but finding Clojure developers will be incredibly difficult. Thus, the fewer specialists who know the new or "unpopular" technology, the more expensive their price tag is. Conclusion: old school is good, fresh is also good, but costly.
Certain technologies can be very expensive because licensed solutions often have subscriptions, including fees for traffic, CPU, and usage in general.
Most companies that employ software systems spend a considerable part of their money on the system's maintenance since the work with the product doesn't end when it's released. When choosing a tech stack and hiring developers with the corresponding expertise, mind such expenditures. Product maintenance often includes spending on the solution's optimization, functionality expansion, bug identification, fixing, etc. Hence, consider opting for cheaper open-source technologies that can be updated and changed without limitations.
Knowing these, you can already come up with a few ideas. And if you did, share your thoughts in the comment. I think there are 3 main ways to save budget.
You can use ready-made solutions. It could be the perfect recommendation for startups with limitations in terms of budget and for businesses who want to check their idea with MVP.
Cross-platform tools for mobile development are an option for you if you want to create a competitive mobile app, but budget restrictions put lots of pressure. You can always save money by employing cross-platform tools instead of native technologies.
And the last option would be finding an experienced and proven software vendor. This could be the most costly option, but it has many benefits. The software vendor will understand your needs, provide proactive solutions to support your vision, and be a trustworthy partner. The professional software company will also assist you in lowering the charges of your tech stack. They are experts in their field and will undoubtedly advise you on cost-cutting measures. If you think this is the option for you, google something like outsourcing/offshoring/nearshoring or check this resource; it might help.
So, share your thoughts in the comment. What technology stack do you use for your project? Need some more info on this topic? Here.
The biggest thing I look for in my tech stack is Productivity - how fast, cheap, and effective it is at accomplishing the goal. All the costs you mention are factors in this.
Another one though is experience - if you and your team is familiar / experienced with a stack they are likely much more likely to be productive in it. So I like to use similar stacks in most of my projects - utilizing the most productive technologies I've found so far.
Here's the tech stack I've used for most of my projects in the past year:
Many of these aren't widely used (yet). A few (SvelteKit) are just now reaching some level of maturity. Some (containers) incur an upfront maintenance cost for the promise of long-term productivity.
But I've found this to be the simplest, most scalable stack for launching my projects / businesses quickly and reliably.
For more on why I like this stack, check out: https://hamy.xyz/labs/2022-11-up-and-running-cloudseed
For some reason we decided to go for the "coolest technology" that we didn't have that much experience with when we started our first project. Then we noticed how slow we were working because of that and decided to rebuild the dashboard with tech that we were more comfortable with. I think it took us two weeks to rebuild it, and now we're working faster than ever! :)
It looks like that's a story with a good ending! Even if you had yet to have the most pleasant experience with the newest technology, the time spent on it, learning, and trying to make the best for your project made you a better professional.
Good luck with your project! 💪
Thanks for sharing such a detailed guidance. As most of the thing which you discussed here we are using for https://researchpaperwriter.org/ and will try to focus the things which we don't discuss. Really appreciate your guidance.
I really appreciate that you find it useful! Thx for sharing.