Since the backend is fastAPI, why the "app._api" have not get or post methods

[jinhong-china]

1. In my understanding, the native backend of Reflex is not a complete fastAPI, without an openAPI docs, get and post method, or include routers. If my web application needs to provide API services externally, does it have to write a separate fastAPI application and use the api_tranformer method to integrate the web and API together?
2. I want to know where the performance boundary of Reflex is? I am conducting technical selection for a project that integrates OA, ERP, CRM and other functions and provides API services externally On a regular 8-core 16GB configuration server, a QPS of at least 300+is required (excluding external APIs, the overall QPS may need reach 600+) I don't know if Reflex can meet it? Can it support multiple processes?
   

[masenf]

The reflex backend uses Starlette now, which is also what FastAPI is based on. If you need to generate docs and other features provided by FastAPI, it is recommended to use the api_transformer.

Performance will vary a lot based on what the app is doing. Because reflex uses websockets, there is an inherent limit in concurrent users, because each user will consume some server resources, even if the user is essentially idle. For production deployments, we recommend using redis, which enables multi-worker mode and provides better throughput on a single machine.