Comments on: Large Web App Architecture: Yes to Thicker Stack on One Hardware Node, No to Beautiful “Redundant” Spiderwebs http://jawspeak.com/2009/08/19/large-web-app-architecture-yes-to-thicker-stack-on-one-hardware-node-no-to-beautiful-redundant-spiderwebs/ Jonathan Andrew Wolter Fri, 04 Jun 2010 01:08:03 -0400 http://wordpress.org/?v=2.9.2 hourly 1 By: Simplicity is Better for Deploying in Production Web Architectures at JAW Speak http://jawspeak.com/2009/08/19/large-web-app-architecture-yes-to-thicker-stack-on-one-hardware-node-no-to-beautiful-redundant-spiderwebs/comment-page-1/#comment-1348 Simplicity is Better for Deploying in Production Web Architectures at JAW Speak Sat, 30 Jan 2010 18:20:55 +0000 http://jawspeak.com/?p=118#comment-1348 [...] and easily manageable has been the focus of much of my time recently. Last time I talked about spiderweb architecture, because it has attributes of scalability and high availability, yet comes with a hidden cost. [...] [...] and easily manageable has been the focus of much of my time recently. Last time I talked about spiderweb architecture, because it has attributes of scalability and high availability, yet comes with a hidden cost. [...]

]]> By: Someone http://jawspeak.com/2009/08/19/large-web-app-architecture-yes-to-thicker-stack-on-one-hardware-node-no-to-beautiful-redundant-spiderwebs/comment-page-1/#comment-1232 Someone Thu, 17 Sep 2009 03:51:27 +0000 http://jawspeak.com/?p=118#comment-1232 I can't event read this article. That bloody scrolling twitter thing on the side is too distracting! I can’t event read this article. That bloody scrolling twitter thing on the side is too distracting!

]]> By: Gerald Boersma http://jawspeak.com/2009/08/19/large-web-app-architecture-yes-to-thicker-stack-on-one-hardware-node-no-to-beautiful-redundant-spiderwebs/comment-page-1/#comment-1180 Gerald Boersma Wed, 19 Aug 2009 16:55:32 +0000 http://jawspeak.com/?p=118#comment-1180 I think this summarizes the (painful) lessons learned from deploying J2EE applications. Using EJBs to distribute "logical" components resulted in punishing performance, that had to be optimized with direct database queries. At some point, we realized we were spending far too much time working around the J2EE framework. Hence the solution to use POJOs and load-balance / fail-over the complete stack. I think this summarizes the (painful) lessons learned from deploying J2EE applications. Using EJBs to distribute “logical” components resulted in punishing performance, that had to be optimized with direct database queries. At some point, we realized we were spending far too much time working around the J2EE framework. Hence the solution to use POJOs and load-balance / fail-over the complete stack.

]]> By: JoshG http://jawspeak.com/2009/08/19/large-web-app-architecture-yes-to-thicker-stack-on-one-hardware-node-no-to-beautiful-redundant-spiderwebs/comment-page-1/#comment-1177 JoshG Wed, 19 Aug 2009 09:48:28 +0000 http://jawspeak.com/?p=118#comment-1177 Actually it was a little more spiderweby than the first picture indicates. Remember, we had the ESB instances on the App Server which also meant that the App Servers had meshed connections to each other as well as the Backend Services. Drawing it will make the picture less beautiful, which is appropriate as it begins to reflect the torturous mess that it really is. Actually it was a little more spiderweby than the first picture indicates.

Remember, we had the ESB instances on the App Server which also meant that the App Servers had meshed connections to each other as well as the Backend Services.

Drawing it will make the picture less beautiful, which is appropriate as it begins to reflect the torturous mess that it really is.

]]>