⚠️ There is no fixed limit to concurrent processing or any paid plan, as each application architecture has unique characteristics.
Applications designed with development best practices in mind can manage higher request volumes more efficiently than those that are not.
💪 Have my workflows been optimized to accommodate higher traffic volumes?
Failure to optimize workflows for rising traffic can result in inefficiency, scalability challenges, and potential outages. These issues lead to poor user experiences, impacting revenue and growth. If you expect a large number of requests, any response longer than 0.75 seconds should be looked into with a magnifying glass.
When longer workflows are running, a spike in the number of incoming requests could clog the server. Enhancing the performance of your most frequently used endpoints will enable you to handle more concurrent processing.
🕙 Do I know my number of Requests Per Second (RPS) at peak times?
Tracking RPS provides valuable insights into system performance, helping identify resource strain, peak activity, and the need for scaling or optimization to handle demand effectively.
🚀 Xano Plans
It's important to note that you have a flat fee In Xano for your subscription plan, making costs more predictable and preventing any surprises at the end of the billing cycle. On the flip side, there are processing limits for your instance.
⤴️ For comparison, the Scale 1x plan provides triple the CPU resources of the Launch plan, along with the load balancer, which represents a great performance boost.
📶 If you need more power, the other Scale plans—2x, 4x, and 8x—each offer double the resources of the previous tier and include auto-scaling, making it simpler to test their capabilities with your use case and figure out what works best for your needs.