Blocklet Capacity & Concurrent User Load
Hello Arcblock team/community
I’m doing some capacity planning for a business-facing blocklet (ERP-style workloads, not bursty consumer traffic), and wanted to better understand how user load is handled at the blocklet and node level.
Specifically:
- How does a blocklet handle concurrent users (e.g. dozens to hundreds of active users doing CRUD-style operations at the same time)?
- Are there practical limits where a blocklet would need to be isolated to its own node/server?
- How does the node manage resource allocation between multiple blocklets under load?
Not looking for marketing answers — just trying to understand the architectural boundaries so I can design responsibly. Appreciate any guidance.
Thank you,
12inchapps.com
2 条回复
Blocklet itself doesn’t impose a hard limit on concurrency. How much it can handle mainly depends on the machine configuration and usage patterns.
Based on our testing, under a typical server setup the core services provided by Blocklet Server are generally not the bottleneck, with capacity well beyond the “tens or hundreds of users” range.
In practice, unless you’re dealing with a very large organization with tens of thousands of users, most companies with a few thousand users don’t need to worry much about this. The real things to watch are usually the business Blocklet’s own database usage and more complex logic.
As you mentioned, this is more of an ERP-style workload rather than bursty consumer traffic. In this case, the critical factors are mostly in the Blocklet’s own implementation, with database design and optimization being especially important.
Thanks for the detailed answer — really reassuring and matches what we’re seeing. Appreciate the insight .
The ERP-style workload framing makes a lot of sense. Now that scaling feels settled, we’re thinking more about distribution and billing — especially running our own storefront and abstracting DID Space costs for customers. Curious if that aligns with how you see the platform evolving.