When comparing Strapi vs Java, the Slant community recommends Strapi for most people. In the question“What are the best backend web frameworks?” Strapi is ranked 32nd while Java is ranked 42nd. The most important reason people chose Strapi is:
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Auto-generate REST APIs
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Pro Users, groups and permissions
Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.
Pro Out-of-the-box administration panel
Easy way to manage your application. This panel allows you to add/edit/delete entries for your APIs, manage your users, groups and permissions. In the future, it will be such as WordPress-like administration panel dedicated to your application.
Pro Verbosity
It makes it easy to debug and to read code.
Pro Mature ecosystem
The language and all its tools have enough time to age and they've aged well.
Pro Type-safe
It is easier to catch errors sooner.
Cons
Con Memory hungry
Running the virtual machine, application server and application itself consumes significant amount of resources.
Con Unnecessarily obtuse and verbose
If you like typing 40 lines of code to open a file, Java is the language for you. If, on the other hand, you’d actually like to get something done, look elsewhere.
Con Oracle
Enough said.
In more detail: Oracle has acquired Java from Sun and continues to surround it with controversy ever since (legendary lawsuit with google, money extortion from the enterprise users etc.).
