So just choose one and kickstart your product. But if you are building something really specific, and there's a language and a framework build especially for that, then you should definitely chose that tech.īut most of the time, the problems we are trying to solve can be easily taken care of with any of the above mentioned languages and their respective frameworks. If you are in the phase of doing POCs, just build and get it done. To avoid those issues, choose a more widely used, well-documented language. You don't need to get stuck on issues that might come from the new language in town. So get your product out as soon as possible. You can choose any language, just pick which one is most comfortable for you.Īnd remember – you are building an MVP (Minimum Viable Product), and will be in the process of creating a POC (Proof of Concept). So choose a language that has some real good support in the industry, like Javascript, Python, Java, or Go to name a few. Having said this, it's rare, because there are very few people who are Javascript Ninjas, or Python Panthers, or whatever funky names are out there. My advice is to choose a language you are most comfortable with and know the intricacies of in and out. Choose the CORRECT language and framework (for your project)Ĭhoosing the correct language and framework for your product is tricky, and there's no particular silver bullet for this. So without further build-up, here's the checklist you should go through while building a Backend Architecture for a product from scratch. I finally decided to create this checklist of things that you should consider before hitting that deploy button for the first time. And they will come back to bite you in later stages of the product cycle. There are so many things involved in building an architecture from scratch that you will totally forget certain pieces. I always wished there was a checklist to follow while building a product from the ground up. I have myself worked on a handful of early stage products, and to be honest, I did make mistakes. Otherwise, please share with those who will definitely love this :P Where this guide came from So if you are interested in knowing the nitty-gritty of the technologies involved, then proceed. NOTE - The following is related to building software architectures from scratch. This isn't a time to experiment, it's the time to execute. All you need is the right guide to help you figure out what you should and shouldn't do. These moments are rare, but when they happen you need to jumpstart at the right time. The first mover advantage is yours to take. ![]() You know investors will love it, and you just can't wait to start building the product. You finally figured out your business model, and it all falls into place. You wake up one morning to have your cup of coffee and voilà, the Eureka moment is here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |