Building VS Buying

Creating articles for purchasing software applications is a powerful tool to make your business more efficient and effective. Many people try to use commercially available commercial software (COTS) only to find that their specific needs require professionally developed software. Others insist that vendors reinvent the circle by developing software in areas offering mature, reliable, and relatively inexpensive versions. Building your own software and system has several major advantages.

There are many options for building and buying spectrum. There is an open source (build) on one side and a complete build (SaaS) solution on the other side (purchase). Although all options have advantages and disadvantages, simple diagrams explain the concept of landscape: the most distant aspects of build are open source protocols such as WebSockets and HTTP Long Polling. These are just simple protocols. In other words, you can manage everything and make it function. This includes starting up the back-end infrastructure, maintaining it, building a new SDK to support new devices and languages, everything else.

In the harsh world of today's SaaS, there is constant debate about construction and purchasing. In most cases, buying rather than buildings is more valuable, but sometimes we will push this discussion extremely and ultimately pay a fairly small amount. As a result, our developers are beginning to forget how the basic elements of the Internet work. Again, in the competitive world, you only need to purchase small services and combine them to serve you. Given our many choices of today, this is perfectly acceptable. However, you need to balance learning and dependencies on other things, building and buying different services, or hosting your own cloud-based solution. Given the complexity and scale of processing at Go - Jek, I think it 's important to lean towards this build. That said, it is important to build it correctly and always combine it with strategic thinking.

When evaluating the ratio or selection of builds to purchase, it is important to rearrange the way of thinking and process solutions as openly and objectively as possible. I do not care whether we can make our products from scratch or integrate a series of solutions that we skillfully purchased, except for purists. People care about whether our products are effective and provide excellent value to our customers. While these are not a comprehensive feature set, it is important that there is a clear distinction between key product functions (marketing, voting) and the required system and process architecture (server environment, CI / CD pipeline) . Your product has its own and unique features, and almost all modern application systems have building capability