Open-API-Base
We have seen a lot of craze towards "services" that allow companies to reduce costs (because let's face it, it's all about the money) by spending less on Development.
With such a need, tools like ChatGPT, LowCode such as ReTool, and NoCode such as Softr, are becoming more and more popular and appealing.
Such tools provide a lot of flexibility and can get your product out of the door quickly. However, at some point, you will hit a roadblock. There will be features that are not implemented, or they will force you down a specific path and eventually get locked-in into their service.
That is why I still prefer wholly owned products, in which the codebase is fully developed. Of course, not everyone has the resources to employ a complete team of developers with the experience needed to launch a quality product. Some might refer to an outside agency, do heavy prototyping using Adobe or similar “mock-up tools” and some prefer to take the risk and set up their own tech team.
All the above-mentioned are fully reasonable approaches to spinning up your new product, creating demos, or rewriting an existing service. However, I want to focus on the last one. The companies that set teams to failure by reducing their total budget (usually in terms of quality or quantity) while still expecting the output of a fully-fledged team.
I have written APIs from scratch, be it for demos, prototypes, side-projects, or internal services, re-writing existing APIs countless times, and constantly repeating basic structures and patterns by copy-pasting files from existing projects. That is why, I have set up Open-API-Base.
Open-API-Base is a free API written, with the aim to provide a fully-fledged API system that can support your project from start to thousands of users/calls, etc. without the need for external services except infrastructure components such as Databases, Cache layers, Mailing systems, etc.
How can this help?
The repository will be a huge boost for any team that wishes to start over with a focus on speed and quality. However, as it is expected some features, or approaches might not be easy to understand (especially when taking over such a huge system). That is why the whole development will be fully documented using Twitter under this Thread and via blog posts here.
The repository can be found here. Feel free to contact me and happy coding!
Photo by Dayne Topkin on Unsplash