Re: How can isis be made web scale

2017-02-22 Thread Martin Grigorov
On Tue, Feb 21, 2017 at 6:39 PM, Dan Haywood 
wrote:

> Hi Martin,
> Do you know, does web.de use stateful or only stateless pages to hit those
> volumes?
>

The application is stateful.
But it uses many custom components which make use of JS event delegation
and shared Wicket IResources to keep the pages small and reduce page
locking both at the client and server sides.


>
> If only the latter then we can't infer too much from that because Isis
> primarily uses stateful pages.
>
> If the former, then do you know what size of web farm they run to get that
> scale, and how do they manage http sessions?
>

I don't know what kind of hardware is in use.
The http sessions are replicated with Memcached (
https://github.com/magro/memcached-session-manager). But the session is
very small. It keeps just the minimal info to load user data from the DBs.


>
> Thx
> Dan
>
> On Tue, 21 Feb 2017, 17:33 james agada,  wrote:
>
> > Hmm. The device infront of the keyboard is me ?
> > So is the issue with scaling Isis the framework or is it Isis usage of
> > Wicket?
> >
> > On Tue, Feb 21, 2017 at 6:16 PM, Martin Grigorov <
> > martin.grigo...@gmail.com>
> > wrote:
> >
> > > On Feb 21, 2017 7:09 PM, "james agada"  wrote:
> > >
> > > Thanks. My summary is
> > >
> > > 1. Major constraint is Wicket.
> > >
> > >
> > > BULLSHIT!!!
> > > Pardon my French!
> > > The major constraint is the device in front of the keyboard!
> > > web.de is built on Wicket and serves 18M+ users. 200-500K
> > simultaneously!
> > >
> > >
> > > 2. If you build your own view and interface to Isis, then you can scale
> > DB
> > > and app server as best.
> > >
> > > CQNZ claims to have an architecture that scales but it is not
> documented
> > > anywhere.
> > > It will be nice to have a mobile UI that can be as sophisticated as the
> > > Wickets version and also available out of the box.
> > > Many things to chew.
> > >
> > >
> > > +1
> > >
> > >
> > > On Mon, Feb 20, 2017 at 9:53 PM, Dan Haywood <
> > d...@haywood-associates.co.uk
> > > >
> > > wrote:
> > >
> > > > Wicket is stateful (at least Apache Isis' use of it is), so I
> wouldn't
> > > > classify this as web-scale; as Bilgin says you will need to develop a
> > > > custom UI and use the REST API (Restful Objects viewer *is*
> stateless).
> > > I
> > > > believe that Cesar's application [1] takes this approach.
> > > >
> > > > Also as Bilgin says, the DB is therefore likely to be the biggest
> > > > contention point.  RDBMS can of course scale a long way, so you don't
> > > > necessarily need to go the NoSQL route, but if that did turn out to
> be
> > > > necessary then DataNucleus does support other datastores such as
> Mongo.
> > > My
> > > > advice would be to build a performance test rig and do the stress
> > testing
> > > > up front so you can learn more about the relative performance
> > > > characteristics.
> > > >
> > > > HTH
> > > > Dan
> > > >
> > > > [1] http://isis.apache.org/powered-by.html#_powered-by_cqnz
> > > >
> > > >
> > > >
> > > > On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam 
> wrote:
> > > >
> > > > > 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 
> > > 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
> > > > >
> > > >
> > >
> >
>


Re: How can isis be made web scale

2017-02-21 Thread Dan Haywood
Hi Martin,
Do you know, does web.de use stateful or only stateless pages to hit those
volumes?

If only the latter then we can't infer too much from that because Isis
primarily uses stateful pages.

If the former, then do you know what size of web farm they run to get that
scale, and how do they manage http sessions?

Thx
Dan

On Tue, 21 Feb 2017, 17:33 james agada,  wrote:

> Hmm. The device infront of the keyboard is me ?
> So is the issue with scaling Isis the framework or is it Isis usage of
> Wicket?
>
> On Tue, Feb 21, 2017 at 6:16 PM, Martin Grigorov <
> martin.grigo...@gmail.com>
> wrote:
>
> > On Feb 21, 2017 7:09 PM, "james agada"  wrote:
> >
> > Thanks. My summary is
> >
> > 1. Major constraint is Wicket.
> >
> >
> > BULLSHIT!!!
> > Pardon my French!
> > The major constraint is the device in front of the keyboard!
> > web.de is built on Wicket and serves 18M+ users. 200-500K
> simultaneously!
> >
> >
> > 2. If you build your own view and interface to Isis, then you can scale
> DB
> > and app server as best.
> >
> > CQNZ claims to have an architecture that scales but it is not documented
> > anywhere.
> > It will be nice to have a mobile UI that can be as sophisticated as the
> > Wickets version and also available out of the box.
> > Many things to chew.
> >
> >
> > +1
> >
> >
> > On Mon, Feb 20, 2017 at 9:53 PM, Dan Haywood <
> d...@haywood-associates.co.uk
> > >
> > wrote:
> >
> > > Wicket is stateful (at least Apache Isis' use of it is), so I wouldn't
> > > classify this as web-scale; as Bilgin says you will need to develop a
> > > custom UI and use the REST API (Restful Objects viewer *is* stateless).
> > I
> > > believe that Cesar's application [1] takes this approach.
> > >
> > > Also as Bilgin says, the DB is therefore likely to be the biggest
> > > contention point.  RDBMS can of course scale a long way, so you don't
> > > necessarily need to go the NoSQL route, but if that did turn out to be
> > > necessary then DataNucleus does support other datastores such as Mongo.
> > My
> > > advice would be to build a performance test rig and do the stress
> testing
> > > up front so you can learn more about the relative performance
> > > characteristics.
> > >
> > > HTH
> > > Dan
> > >
> > > [1] http://isis.apache.org/powered-by.html#_powered-by_cqnz
> > >
> > >
> > >
> > > On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam  wrote:
> > >
> > > > 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 
> > 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
> > > >
> > >
> >
>


Re: How can isis be made web scale

2017-02-21 Thread james agada
Hmm. The device infront of the keyboard is me ?
So is the issue with scaling Isis the framework or is it Isis usage of
Wicket?

On Tue, Feb 21, 2017 at 6:16 PM, Martin Grigorov 
wrote:

> On Feb 21, 2017 7:09 PM, "james agada"  wrote:
>
> Thanks. My summary is
>
> 1. Major constraint is Wicket.
>
>
> BULLSHIT!!!
> Pardon my French!
> The major constraint is the device in front of the keyboard!
> web.de is built on Wicket and serves 18M+ users. 200-500K simultaneously!
>
>
> 2. If you build your own view and interface to Isis, then you can scale DB
> and app server as best.
>
> CQNZ claims to have an architecture that scales but it is not documented
> anywhere.
> It will be nice to have a mobile UI that can be as sophisticated as the
> Wickets version and also available out of the box.
> Many things to chew.
>
>
> +1
>
>
> On Mon, Feb 20, 2017 at 9:53 PM, Dan Haywood  >
> wrote:
>
> > Wicket is stateful (at least Apache Isis' use of it is), so I wouldn't
> > classify this as web-scale; as Bilgin says you will need to develop a
> > custom UI and use the REST API (Restful Objects viewer *is* stateless).
> I
> > believe that Cesar's application [1] takes this approach.
> >
> > Also as Bilgin says, the DB is therefore likely to be the biggest
> > contention point.  RDBMS can of course scale a long way, so you don't
> > necessarily need to go the NoSQL route, but if that did turn out to be
> > necessary then DataNucleus does support other datastores such as Mongo.
> My
> > advice would be to build a performance test rig and do the stress testing
> > up front so you can learn more about the relative performance
> > characteristics.
> >
> > HTH
> > Dan
> >
> > [1] http://isis.apache.org/powered-by.html#_powered-by_cqnz
> >
> >
> >
> > On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam  wrote:
> >
> > > 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 
> 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
> > >
> >
>


Re: How can isis be made web scale

2017-02-21 Thread Martin Grigorov
On Feb 21, 2017 7:09 PM, "james agada"  wrote:

Thanks. My summary is

1. Major constraint is Wicket.


BULLSHIT!!!
Pardon my French!
The major constraint is the device in front of the keyboard!
web.de is built on Wicket and serves 18M+ users. 200-500K simultaneously!


2. If you build your own view and interface to Isis, then you can scale DB
and app server as best.

CQNZ claims to have an architecture that scales but it is not documented
anywhere.
It will be nice to have a mobile UI that can be as sophisticated as the
Wickets version and also available out of the box.
Many things to chew.


+1


On Mon, Feb 20, 2017 at 9:53 PM, Dan Haywood 
wrote:

> Wicket is stateful (at least Apache Isis' use of it is), so I wouldn't
> classify this as web-scale; as Bilgin says you will need to develop a
> custom UI and use the REST API (Restful Objects viewer *is* stateless).  I
> believe that Cesar's application [1] takes this approach.
>
> Also as Bilgin says, the DB is therefore likely to be the biggest
> contention point.  RDBMS can of course scale a long way, so you don't
> necessarily need to go the NoSQL route, but if that did turn out to be
> necessary then DataNucleus does support other datastores such as Mongo.
My
> advice would be to build a performance test rig and do the stress testing
> up front so you can learn more about the relative performance
> characteristics.
>
> HTH
> Dan
>
> [1] http://isis.apache.org/powered-by.html#_powered-by_cqnz
>
>
>
> On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam  wrote:
>
> > 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  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
> >
>


Re: How can isis be made web scale

2017-02-21 Thread james agada
Thanks. My summary is

1. Major constraint is Wicket.
2. If you build your own view and interface to Isis, then you can scale DB
and app server as best.

CQNZ claims to have an architecture that scales but it is not documented
anywhere.
It will be nice to have a mobile UI that can be as sophisticated as the
Wickets version and also available out of the box.
Many things to chew.

On Mon, Feb 20, 2017 at 9:53 PM, Dan Haywood 
wrote:

> Wicket is stateful (at least Apache Isis' use of it is), so I wouldn't
> classify this as web-scale; as Bilgin says you will need to develop a
> custom UI and use the REST API (Restful Objects viewer *is* stateless).  I
> believe that Cesar's application [1] takes this approach.
>
> Also as Bilgin says, the DB is therefore likely to be the biggest
> contention point.  RDBMS can of course scale a long way, so you don't
> necessarily need to go the NoSQL route, but if that did turn out to be
> necessary then DataNucleus does support other datastores such as Mongo.  My
> advice would be to build a performance test rig and do the stress testing
> up front so you can learn more about the relative performance
> characteristics.
>
> HTH
> Dan
>
> [1] http://isis.apache.org/powered-by.html#_powered-by_cqnz
>
>
>
> On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam  wrote:
>
> > 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  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
> >
>


Re: How can isis be made web scale

2017-02-20 Thread Dan Haywood
Wicket is stateful (at least Apache Isis' use of it is), so I wouldn't
classify this as web-scale; as Bilgin says you will need to develop a
custom UI and use the REST API (Restful Objects viewer *is* stateless).  I
believe that Cesar's application [1] takes this approach.

Also as Bilgin says, the DB is therefore likely to be the biggest
contention point.  RDBMS can of course scale a long way, so you don't
necessarily need to go the NoSQL route, but if that did turn out to be
necessary then DataNucleus does support other datastores such as Mongo.  My
advice would be to build a performance test rig and do the stress testing
up front so you can learn more about the relative performance
characteristics.

HTH
Dan

[1] http://isis.apache.org/powered-by.html#_powered-by_cqnz



On Mon, 20 Feb 2017 at 12:58 Bilgin Ibryam  wrote:

> 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  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
>


Re: How can isis be made web scale

2017-02-20 Thread Bilgin Ibryam
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  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


How can isis be made web scale

2017-02-20 Thread james agada
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