Hello,

I am adding a new sub-set of services for my users in relation to content delivery and streaming.

I was thinking about developing a service that uses catbox.moe as a "hosting provider" with my API logic sitting in-between acting as a controller.

When a user saves a video on my platform, I save it to catbox.moe, than create a URL for the end-user. I then save a reference to the database so that when an end user requests the URL, I retrieve the initial content from catbox.moe and stream it back to the user or create a download link for it.

The goal is to provide cloud storage & video streaming solutions without hosting the content myself.

Is this a good approach? or a bad idea? I want to consult others before going ahead and developing this tool.

I'm facing issues scaling my applications and services. I want to add a new frontend service to the cluster for users to interact with the API.

Currently, I'm considering setting up a Flask blueprint to handle calls to engines 2 and 4. Additionally, I'm planning to migrate engine 2 to FastAPI.

The main issue is that the video generator can only handle 12-16 concurrent users. I'm running Gunicorn with 16 workers and a 120-second request timeout because the video generator occasionally hangs.

Is there a way to package multiple backend services into Docker containers and monitor them with an application on engine 1? Would this approach allow more users to access these services simultaneously?

If that is not a reasonable approach, I am open to doing things differently.

Service engine 2 startup command is;

gunicorn -w 16 --timeout 120 -b 127.0.0.1:8000 wsgi:app

My current setup is;

``` Service Engine 1 (Flask, Sqlite3); Blog posts, User Authentication, Administration Services the main frontend website that face the users Administers the entire cluster including all the other services and frontends.

Service Engine 2 (Flask, Sqlite3); Video generator and editor, link extractor, and other tools that need server side prossesing

Service Engine 3 (Fastapi, Sqlite3); Chat service (rooms, user to user, comments)

Service Engine 4 (Fastapi, Sqlite3); API, an api that the cluster is based around, scrapers and other automations.

Worker (Node); Used for language model requests. ```

I currently have an API that is gaining traction. I would like to market towards people that are able to use APIs, however there is a technical barrier when It comes to requesting an endpoint, saving data, building a script around that, etc.

Should I build a web application that allows non-technical users to access the data from the API? Or, Is that a waste of time for the effort put in?