Isis relies heavily on a DB which is accessed through JDO. So if there is JDO storage that can scale as per your requirements the rest of Isis could become web scale.
If you find that Wicket is not web scale, you could create your own UI and interact with Isis through its REST API. There is also a multi-tenancy plugin which is required quite often for web-scale/SaaS use cases that might be useful too. HTH, On 20 February 2017 at 11:06, james agada <okwuiag...@gmail.com> wrote: > Can Isis be scaled to handle web scale traffic - hundreds of thousands.l of > simultaneous users? What are the bottlenecks? What architectural patterns > work? What data store should be considered? > Rgds -- Bilgin Ibryam Camel Committer at ASF & Integration Architect at Red Hat Blog: http://ofbizian.com | Twitter: @bibryam Camel Design Patterns https://leanpub.com/camel-design-patterns Instant Apache Camel Message Routing http://www.amazon.com/dp/1783283475
