DEV Community

Discussion on: My experience building backends with Booster Framework

Collapse
 
alvaroloes profile image
Álvaro López Espinosa

I can not agree more.

I've been years working for a large company that uses a microservices architecture with Java as its main language. I'm not exaggerating when I say that I spent 20% of my time actually writing Java.

The rest was dealing with database configuration, bugs like running out of DB connections, SQL query optimizations, server problems (instances going down, log files getting too long and running out of space, insufficient memory because some Java service grow unexpectedly, etc.), fighting with deployment scripts, scaling server instances, configuring Nginx, dealing with JSON serialization, and a large etc.

When I started using Booster Framework to build backend applications, it seemed like magic. I didn't need to think about any of this, just designed my models and write the business logic. Then hit "boost deploy" and done 🤯 .

Disclaimer: I'm one of the core developers of the Booster Framework, but this doesn't change any of the words I have written. In fact, we started building the framework because of all this suffering we had in our daily work. But it was not after I first used the first version (after many months of developing) when my mind exploded and really got excited.
It is hard to explain, it is better if you experience it.