2

I could think of these options (Note: not all of them are flask specific). Cap your file size for upload. Compress the file before upload. Chunk the file, you can check this. Stream the file during upload, you will not be able to handle much requests if you keep them all in memory. (as @joshp has mentioned in the comments). Buff it up, provide more ...


2

If this This means the web developer that is creating the GUI application would need to be in communication with the API devs... who may or may not be in the same time zone etc. is your core issue, your documentation is lacking. Microservices should be self-explanatory enough that barely any dev-to-dev communication is needed. Typically it's just an API ...


2

One option is to have 'Journey' or 'ProcessFlow' microservices where there are back-end micro-services that manage the process flow (or journey) through a state-machine. The state-machine captures the current process state of the end-user and provides an API where the front-end can query the possible next state. This removes the need for the front-end to ...


2

It's not possible to know for sure whether caching your data in Redis would be worthwhile without more information, but: Don't jump to the conclusion that you need to cache the data in Redis. Every dependency you add to a project has a cost. Once you add Redis, you have added one more potential source of problems. When debugging your program, you will now ...


Only top voted, non community-wiki answers of a minimum length are eligible