Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 86757200C31 for ; Wed, 8 Mar 2017 08:49:36 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 850F6160B83; Wed, 8 Mar 2017 07:49:36 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CB1F7160B75 for ; Wed, 8 Mar 2017 08:49:35 +0100 (CET) Received: (qmail 25353 invoked by uid 500); 8 Mar 2017 07:49:34 -0000 Mailing-List: contact users-help@isis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@isis.apache.org Delivered-To: mailing list users@isis.apache.org Received: (qmail 25340 invoked by uid 99); 8 Mar 2017 07:49:34 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Mar 2017 07:49:34 +0000 Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5D2EB1A0620 for ; Wed, 8 Mar 2017 07:49:34 +0000 (UTC) Received: by mail-lf0-f42.google.com with SMTP id k202so11121165lfe.1 for ; Tue, 07 Mar 2017 23:49:34 -0800 (PST) X-Gm-Message-State: AMke39ld1OQXkx1JZYcaOv/9iPBY02g7PHzy9qV1TVeFWtc89+x225rosYJFjWEaLZaH0kuASX6c41GYAQFIZA== X-Received: by 10.25.17.100 with SMTP id g97mr1203319lfi.10.1488959372744; Tue, 07 Mar 2017 23:49:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.216.67 with HTTP; Tue, 7 Mar 2017 23:48:52 -0800 (PST) In-Reply-To: References: From: Martin Grigorov Date: Wed, 8 Mar 2017 08:48:52 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Apache Isis Questions - reg To: users Content-Type: multipart/alternative; boundary=001a113fc35e7f6416054a335e8a archived-at: Wed, 08 Mar 2017 07:49:36 -0000 --001a113fc35e7f6416054a335e8a Content-Type: text/plain; charset=UTF-8 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 < karthiosx@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 > > --001a113fc35e7f6416054a335e8a--