<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 12, 2008, at 5:53 AM, Chris Dawson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I'm new to Seaside and am reading the great Seaside tutorial here: <a href="http://www.swa.hpi.uni-potsdam.de/seaside/tutorial">http://www.swa.hpi.uni-potsdam.de/seaside/tutorial</a>. I am somewhat unimpressed with the section on persistence. I'm looking for advice on how to build my application so that I can scale when needed. Should I be using GemStone/S? Or, another OOP database, like GOODS? GOODS scares me as it looks like it is supported by an individual, not a community or company. Any advice is appreciated. What attracted me to Seaside was precisely the notion that I could avoid dealing with scaling problems like you see in Ruby on Rails.<br> <br>Chris</blockquote><div><br></div><div>Hi Chris,</div><div><br></div><div>Welcome to Seaside. I've been reading the printed copy of the Potsdam tutorial and like it as well. One thing to note is that it is specifically tied to Squeak, so does not reflect the commercial offerings. For example, I think you will find that Cincom's approach (based on GLORP) will provide a very strong tie to a variety of industrial strength relational databases. See James Robertson's bog (<a href="http://www.cincomsmalltalk.com/blog/View.ssp)">http://www.cincomsmalltalk.com/blog/View.ssp)</a> for more on that approach.</div><div><br></div><div>Of course, if you are building a new application and are not tied to a relational database, I'd recommend GemStone/S (but then I'm employed by GemStone ;-). We believe that GemStone's contribution to Seaside is, of course, persistence, scaling, and simplicity (avoiding O/R mapping). As to scaling, the design limits exceed whatever hardware you are likely to purchase (number of machines, CPUs, amount of RAM, amount of disk, etc.). We have (non-Seaside) customers with hundreds of machines connected to the same database, others with thousands of concurrent database connections, databases of hundreds of GB, thousands of transactions per second, response times measured in low milliseconds, etc. </div><div><br></div><div>GemStone/S Web Edition is available at no cost, even for commercial use, with the primary limitation of 4 GB of disk. For more information see <a href="http://seaside.gemstone.com">http://seaside.gemstone.com</a>. Dale's blog (<a href="http://gemstonesoup.wordpress.com/)">http://gemstonesoup.wordpress.com/)</a> has a series of posts on scaling, as well as other good, up-to-date information. The Seaside work is in an open beta where anyone who asks is given access to the latest download.</div><div><br></div><div>James Foster</div><div>GemStone Systems, Inc.</div><div><br></div><blockquote type="cite"><br></blockquote></div></body></html>