Hi,
Even that you have big amount of items/entities usually you will not going
to show more than 200-300 of them at a time.
I.e. most probably you are going to using some kind of pagination both in
UI and in your SQL/NOSQL queries.
Both Wicket and REST interfaces will deal easily with this.
My application is pure Wicket, no Isis, and we have an Elasticsearch index
with 300M documents. There are no problems to present those to the users.
Even if they were 3 billions it would be the same - we show 300 items at
the time in a table with infinite/virtual scrolling.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Wed, Mar 8, 2017 at 4:38 AM, Karthikeyan Alagarswamy <
karthi...@outlook.com> wrote:
> Hi Team,
>
> Thanks for your contributions to open source software.
>
> I had a chance to look at Apache Isis for a new web application yet to be
> developed for my organization. It's fantastic especially the domain driven
> approach.
>
> However I have some questions on the scalability in production. My
> application will have less than a hundred users and might be deployed in
> less than 10 servers. But, the application will have to handle and process
> tens of thousands of heavy weight objects. These are like maximum numbers.
> Having said that, do you see any scaling and performance issues, if I go
> with Apache Isis? Can you also suggest some ways to have higher performance
> with less hardware? And your recommendations on whether to go with Wicket
> or a REST based app.
>
> Your help would be highly appreciated.
>
> Regards,
> Karthi,
> karthiteach.com
>
>
