• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Scaling WebObjects at the web-server/proxy level
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Scaling WebObjects at the web-server/proxy level


  • Subject: Scaling WebObjects at the web-server/proxy level
  • From: "Brook, James" <email@hidden>
  • Date: Tue, 26 Feb 2013 14:10:09 +0000
  • Thread-topic: Scaling WebObjects at the web-server/proxy level

I have a question about a general approach to high scalability for
WebObjects applications. In particular I am interested in how people
handle the incoming requests before they reach the application instances.
I am confident that the Java applications scale. The sort of load I am
talking about is in the order of 10s of thousand of requests per second.
Presently we use Apache 2.2 with the 'worker' MPM and we experience
serious bottlenecks in mod_WebObjects under load (perhaps because of
Solaris).

So, I guess the questions are:

* Do people use mod_WebObjects for handling 10s or even 100s of thousands
of requests per second?

* Do people use Apache? If so, is everyone using prefork (not very
scalable) or do people use other MPMs like 'worker' or even the 'event'
MPM in Apache 2.4? I don't have much confidence that the present WO
adaptor code is thread safe.

* Are people exposing their WebObjects apps behind alternative web servers
with an 'event loop', e.g. nginx or perhaps directly behind a hardware
load balancer?

* Have people built custom solutions for discovery, load-balancing and
failover that still take advantage of wotaskd, the app heartbeats, etc?
Perhaps Java based with Netty or some sort of alternative modern adaptor?

* Are people just freezing their config and using Apache with
mod_proxy_balancer?

* Does anyone here serve similar volumes of traffic?


* Finally, is there a need for a more modern proxy for WebObjects? What
direction would be best to take? Are there people who would want to be
involved in building something if there is a perceived need for it? I
think we would happily make a financial contribution for a modern and
elastic deployment stack if someone in the community is interested in
working on it.

I would be really interested to hear if anyone is facing similar
challenges.

Best regards
James






 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Scaling WebObjects at the web-server/proxy level
      • From: Chuck Hill <email@hidden>
  • Prev by Date: ERModern and ERDControllerButton
  • Next by Date: Re: ERModern and ERDControllerButton
  • Previous by thread: Re: ERModern and ERDControllerButton
  • Next by thread: Re: Scaling WebObjects at the web-server/proxy level
  • Index(es):
    • Date
    • Thread