My iOS app project requires a backend server capable of efficiently handling image files and dynamic operations like interacting with a data store such as Redis. Python is my preferred language for the backend development.
After exploring various Python web frameworks and servers including Flask, Bottle, static, and Tornado, I found that they either focus on serving static files during development only or excel in handling dynamic functionalities but lack efficiency in serving static files. This led me to seek a solution that specializes in serving JPEGs rather than generating HTML without forcing Python applications into unfamiliar territory.
I need a web framework that can serve images housed in a directory structure without revealing actual file names to clients. The server should assign unique numeric IDs to each file at startup and routes requests to controller methods responsible for serving the images based on specific client needs such as random access, sequential access, ratings, and other metadata retrieval from a Redis data store.
The backend must effectively serve image/jpeg and application/json formats, comply with modest scalability and concurrency requirements, and avoid relying on redirects. Instead, I aim to eliminate multiple request delays by directly responding to client URLs with image/jpeg content and relevant metadata headers stored in custom HTTP headers.
With these goals in mind, I am seeking recommendations for a suitable solution that aligns with this vision. Should I customize existing projects to meet these specifications, or is there an optimal choice available?
EDIT: Reflecting further on my requirements, I envision a seamless process where a Python program receives request information from nginx or a similar server, processes it internally, and instructs nginx to deliver the requested file from the file system back to the client without revealing any details about the source. Is this scenario feasible with nginx or another tool?