All of our hardware is virtualized. It's allowed us to scale very quickly and easily. As for specific requirements it really depends on the volume you expect.
If your going to run Apache, Tomcat, and your DB on the same machine I'd try to have at least 512mb on a low volume site. You may want to also come up with a plan that will allow you to scale easily, for example put physically separating your layers will make it easier in a hurry to scale them up if necessary. J On Thu, Apr 10, 2008 at 9:48 AM, Oliver Lieven <[EMAIL PROTECTED]> wrote: > > Hi all, > > are there any suggestions or experiences on the (minimum) system/hardware > requirements for running a Wicket based application on a productive > system? > Would e.g. a Virtual Server as offered by most hosting providers be > powerful > enough to run a Java/Tomcat/Wicket/database application? > > I know this cannot be answered in general since it depends on the > application itself (size of app, programmer skills), number of concurrent > users, database, ... and as always: "the more - the better". > > But maybe someone already running a Wicket app in production (e.g. from > one > of the "Sites using Wicket" - > http://cwiki.apache.org/WICKET/sites-using-wicket.html)) can share > information and experiences on this... (sorry if I've overseen > information > on this topic in the docs, Wiki or forum). > > Thanks in advance, > Oliver > > > -- > View this message in context: > http://www.nabble.com/System-requirements-for-running-wicket-app-in-production-tp16608729p16608729.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
