Jugurtha on Ask HN: What would you use to build a mostly CRUD back end today?

Comment on Ask HN: What would you use to build a mostly CRUD back end today?

  - Stack:

    - Application:
      - Flask[0]
      - Flask-Admin[1] (maybe for the initial prototype)
      - SQLAlchemy --> PostgreSQL
      - Gunicorn --> Nginx
      - Celery[2] (long-running background jobs)


    - Monitoring:
      - Sentry[3]
         
    - Analytics:
      - PostHog[4]

    - Packaging:
      - Docker[5] & docker-compose

I may use Flask-Admin initially to offload the "CRUD" operations to have an initial prototype fast but then drop it ASAP because I don't want to write a "flask-admin application" to fight against later on. If the application is mainly "CRUD", then Flask-Admin is suitable.

Now...

Would you do a breakdown/list of all the jobs you've done by sector/vertical and by function/role and by application functionality?

- [0]: https://flask.palletsprojects.com

- [1]: https://flask-admin.readthedocs.io/en/latest

- [2]: https://flask.palletsprojects.com/en/2.3.x/patterns/celery

- [3]: https://sentry.io

- [4]: https://posthog.com

- [5]: https://www.docker.com

CwizardOP2y

I prefer not to go into too many details but most contracting I did was for medium sized companies to digitize some of their internal processes (that were previously running on Excel and email, i.e. people emailing excel files around).

In my experience cost is still a big factor. The budget for these projects is usually rather small because it is viewed solely as a cost and not an enabler. The number of users for these internal APIs is rather low and so it seems quite expensive per head.

Comments