Why Herbs?

While most of the current ecosystem is focused, for example, on who has the best HTML rendering time, which is a legitimate issue, we understand that some fundamental issues are not being addressed.

Herbs goes in a completely different direction. Herbs was created to solve fundamental software development problems such as delivering real business value, maintainability and knowledge retention.

Let's delve deeper!

Fast development: Now and Always

With Herbs it is very fast to create a new project. Using the Herbs CLI it is possible to create a new microservice focused on your business problem and in a short time deploy it to your preferred infrastructure.

However, it is not enough to be quick in creating a new project. You need to keep the cost of evolution and maintenance low over the lifespan of the software.

Herbs was designed with maintenance in mind from day one. So you can keep evolving your software with new business demands with the peace of mind that your system won't quickly turn into a big ball of mud.

More Time Spent On The Domain

Software must deliver value to the business. Period. Why spend so much time writing code about worthless things like the URL format in the REST endpoint? POST or PUT? Or rewrite dozens of resolvers for your GraphQL? Postgres ou Mongo?

Some of this discussion has value, but it shouldn't be where we put most of our energy.

With Herbs the focus of the discussion is on delivering value, not the accidental complexity of the software. The time spent is put into specs, use cases, entities, business rules, etc.

Domain Knowledge: Retention and Propagation

Knowing languages and tools is not enough when we are developing software. One also needs to know about the application domain aka "business rules".

So, new team members need to know and become familiar with the business rules. Leaving members cannot take the knowledge with them. Some contexts can be very challenging in this sense, such as specialist domains, difficulty in hiring, high turnover, etc.

With Herbs code and documentation go together. New developers can access the documentation or just read the code to learn about the business. And for those who leave the team, the impact is low because the knowledge is retained in the code.

Enterprise Features Out Of The Box

With Herbs, features such as authorization and execution audits are native. We believe that applications should be safe and reliable.