publishing-strapiv4-heroku VS Strapi

I'm getting conservatively 800 req/sec on Heroku Standard-1x for my Strapi instance this is on mini postgres with the redis LCU cache, benchmarks here https://123dyno.com/blog/cpu-autoscaling-on-heroku-with-123-dyno. I'd highly recommend installing the redis cache if you haven't looked into it, have my setup in a button here if you want to check out the plugin setup https://github.com/123-Dyno/publishing-strapiv4-heroku. It jumps occasionally when cache clears but for the most part is fine.

Recently released a button to deploy Strapi to Heroku if you need a reference for deploying there. Cheapest plan is somewhere between $13-$20ish for your traffic needs, really should not be costing you 110. Migrating over will probably take some work but won't require too much maintenance when setup.

I'm posting a Heroku deploy button for Strapi that I'm maintaining here https://github.com/123-Dyno/publishing-strapiv4-heroku it comes prepackaged with a production scalable setup minus the keys with built in links to Heroku add-ons so it can be setup in less than 10 minutes.

Strapi provides a centralized data managing platform. This makes it easier to organize, update, and maintain the FAQ data. It also automatically generates a RESTful API for accessing the content stored in its database.

https://prisma.io is popular as I understand it. I've been trying out https://strapi.io the last week and am thoroughly impressed.

They both do much more than build queries. One big thing both do is automate database migration calculations. Strapi goes further and gives you a CMS and admin UI on top, as well as doing a lot more of the complex query building from a json object. Both still require a fundamental understanding of the data model and SQL

As of April 2024, Strapi's GitHub repository has garnered 59.7k stars and 7.5k forks, showcasing its widespread adoption. The project has also secured a substantial $45+ million in funding, cementing its position as a prominent player in the headless CMS space.

const pages = await client.GET("/pages", { params: { query: { filters: { // @ts-ignore - openapi generated from strapi results in Record // https://github.com/strapi/strapi/issues/19644 path: { $eq: path, }, }, // @ts-ignore populate: { blocks: { populate: "*" }, }, }, }, });

On a side note. Where do all these endpoints come from? Strapi is open source. We can read the source code. All these endpoint come from the Users and permissions plugin. So, if we go to Strapi on github and browse around the files a bit eventually you will find the auth.js file that contains all of the routes. You can also find the Strapi controllers in there if you're interested.

Strapi

Strapi: The Code Anarchist

Strapi - Open source Node.js Headless CMS 🚀