Re: Here we go again...WebDNA - SQL- Clustering

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66704
interpreted = N
texte = Adam The ability to use one data source such as you have illustrated here is one of the reasons that I am investigating the WebDNA & MySQL solution. Stuart Tremain idfk web developments, sydney, australia On 04 Apr 2006, at 8:58 AM, Adam O'Connor wrote: > Yeah, every enterprise environment I have ever worked with stored > their data via SQL, via one of its many flavors. I don't think you > can compare webdna's native db system with a true RDBMS such a > MySQL, to do so is like comparing apples to oranges. > > Take for example, any of you webdna diehards out there, say you > built an auction website using only webdna. Say this website > initially handled 150k sessions/month, but over time has grown to > over a 1,000,000 sessions per/month. Hypothetically speaking I know > server environment plays a main factor, but even so which databases > platform would you and/or your client prefer a webdna/flat-files > running on a single box or a webdna server piping info to and from > an SQL database server(say a MySQL transactional database running > on its own server). > > Heck to make this more hypothetical, say your website has grown to > 10,000,000 sessions a month, who's to say you wouldn't be able to > purchase additional webcat licenses and cluster web servers through > a load balancer with 1 or /N /SQL servers on the ring. Having this > data running on its own server not only alleviates data processing > for webcat, but also isolates it, making it accessible to just > about any box that has access to it. > > In this scenario, webcat would be quite distinguished. > > I know these examples are large, but really, if you are going to > devote time and effort with a webdev platform, why not ensure it > can handle what the others are capable of handling. > > > > > > > > > Bess Ho wrote: >> Thanks for your kind words. Part of my background is instructor. >> So it is important to clarify the definition and layout the facts. >> >> There are a lot more thoughts on selecting the database in both >> business and technical sense. Flat file makes it too much hassle >> to do any business intelligences, data mining or even reporting. >> It is not scalable for enterprise application. >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On >> Behalf Of >> Adam O'Connor >> Sent: Monday, April 03, 2006 3:16 PM >> To: WebDNA Talk >> Subject: Re: Here we go again... >> >> >> I agree. The fact that you can 'relationalize' web cat simply >> points out that you are a talented scripter. >> >> Generally speaking sometimes tasks are best written with webcat's >> native flat file db system. But in certain cases some of us find >> SQL a better data system, due to its accessibility, reliability, >> and capacity among other things. >> I don't see the need to take a side on which is better, all >> depends what you are using it for. Although I do lean more >> towards the SQL. Quite frankly it is simple to use, so why not >> take advantage and blend your proprietary knowledge with an >> industry-wide technology - in the end you have benefited by >> broadening your skill set by learning to use an industry standard >> data management system. Afterall, by implementing SQL into your >> webdna webapps, you may get more out of webdna. >> >> >> >> >> >> >> Bess Ho wrote: >> >>> It is important to clarify these things to other WebDNA >>> developers so that they can be wiser in selecting database type >>> to start their project. >>> >>> -----Original Message----- >>> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On >>> Behalf Of >>> Donovan Brooke >>> Sent: Monday, April 03, 2006 2:20 PM >>> To: WebDNA Talk >>> Subject: Re: Here we go again... >>> >>> >>> Bess Ho wrote: >>> >>> >>>> Thanks Kenneth. Thanks for clarifying the myth. >>>> >>>> I think it is important for developers to understand the facts. >>> > WebDNA is not "relational" database. By database definition, >>> > you must meet certain criteria to call something "relational" >>> database. >>> >>>> MS Access is not a true database because it didn't meet all the >>>> criteria. >>>> >>>> Bess >>>> >>> Sure it is. >>> If you have data in one text file database that effects another >>> database's >>> records when edited.. you've essentially created a relational >>> database. Now, >>> there are deeper and darker "definitions" of how data is saved / >>> manipulated.. >>> but creating a relational database framework in webdna is not >>> advanced and it >>> is just as secure. >>> >>> Donovan >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Here we go again...WebDNA - SQL- Clustering ( Kenneth Grome 2006)
  2. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  3. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  4. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  5. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  6. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  7. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  8. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  9. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
  10. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  11. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  12. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  13. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  14. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  15. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  16. Re: Here we go again...WebDNA - SQL- Clustering ( Bob Minor 2006)
  17. Re: Here we go again...WebDNA - SQL- Clustering ( Stuart Tremain 2006)
  18. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
Adam The ability to use one data source such as you have illustrated here is one of the reasons that I am investigating the WebDNA & MySQL solution. Stuart Tremain idfk web developments, sydney, australia On 04 Apr 2006, at 8:58 AM, Adam O'Connor wrote: > Yeah, every enterprise environment I have ever worked with stored > their data via SQL, via one of its many flavors. I don't think you > can compare webdna's native db system with a true RDBMS such a > MySQL, to do so is like comparing apples to oranges. > > Take for example, any of you webdna diehards out there, say you > built an auction website using only webdna. Say this website > initially handled 150k sessions/month, but over time has grown to > over a 1,000,000 sessions per/month. Hypothetically speaking I know > server environment plays a main factor, but even so which databases > platform would you and/or your client prefer a webdna/flat-files > running on a single box or a webdna server piping info to and from > an SQL database server(say a MySQL transactional database running > on its own server). > > Heck to make this more hypothetical, say your website has grown to > 10,000,000 sessions a month, who's to say you wouldn't be able to > purchase additional webcat licenses and cluster web servers through > a load balancer with 1 or /N /SQL servers on the ring. Having this > data running on its own server not only alleviates data processing > for webcat, but also isolates it, making it accessible to just > about any box that has access to it. > > In this scenario, webcat would be quite distinguished. > > I know these examples are large, but really, if you are going to > devote time and effort with a webdev platform, why not ensure it > can handle what the others are capable of handling. > > > > > > > > > Bess Ho wrote: >> Thanks for your kind words. Part of my background is instructor. >> So it is important to clarify the definition and layout the facts. >> >> There are a lot more thoughts on selecting the database in both >> business and technical sense. Flat file makes it too much hassle >> to do any business intelligences, data mining or even reporting. >> It is not scalable for enterprise application. >> >> -----Original Message----- >> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On >> Behalf Of >> Adam O'Connor >> Sent: Monday, April 03, 2006 3:16 PM >> To: WebDNA Talk >> Subject: Re: Here we go again... >> >> >> I agree. The fact that you can 'relationalize' web cat simply >> points out that you are a talented scripter. >> >> Generally speaking sometimes tasks are best written with webcat's >> native flat file db system. But in certain cases some of us find >> SQL a better data system, due to its accessibility, reliability, >> and capacity among other things. >> I don't see the need to take a side on which is better, all >> depends what you are using it for. Although I do lean more >> towards the SQL. Quite frankly it is simple to use, so why not >> take advantage and blend your proprietary knowledge with an >> industry-wide technology - in the end you have benefited by >> broadening your skill set by learning to use an industry standard >> data management system. Afterall, by implementing SQL into your >> webdna webapps, you may get more out of webdna. >> >> >> >> >> >> >> Bess Ho wrote: >> >>> It is important to clarify these things to other WebDNA >>> developers so that they can be wiser in selecting database type >>> to start their project. >>> >>> -----Original Message----- >>> From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On >>> Behalf Of >>> Donovan Brooke >>> Sent: Monday, April 03, 2006 2:20 PM >>> To: WebDNA Talk >>> Subject: Re: Here we go again... >>> >>> >>> Bess Ho wrote: >>> >>> >>>> Thanks Kenneth. Thanks for clarifying the myth. >>>> >>>> I think it is important for developers to understand the facts. >>> > WebDNA is not "relational" database. By database definition, >>> > you must meet certain criteria to call something "relational" >>> database. >>> >>>> MS Access is not a true database because it didn't meet all the >>>> criteria. >>>> >>>> Bess >>>> >>> Sure it is. >>> If you have data in one text file database that effects another >>> database's >>> records when edited.. you've essentially created a relational >>> database. Now, >>> there are deeper and darker "definitions" of how data is saved / >>> manipulated.. >>> but creating a relational database framework in webdna is not >>> advanced and it >>> is just as secure. >>> >>> Donovan >>> >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to > digest@talk.smithmicro.com> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> > > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to digest@talk.smithmicro.com> > Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Stuart Tremain

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

triggers.db (1999) [url] link (1998) Re[2]: when is failing to [URL]ize values in a comparison ri (1999) WebCat2.0 acgi vs plugin (1997) SHOWIF/HIDEIF empty fields (2005) BUG in [showif] using ^ (contains) (1997) Holy emails Batman! WebCat's Insane! (2003) math on date? (1997) Credit card processing - UK (1997) WCS Newbie question (1997) More on the email templates (1997) unable to launch acgi in WebCat (1997) -REPOST- WebCat 3 & Aliases (2000) Forms (1997) SiteEdit NewFile.html ? (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) Exclamation point (1997) Postdata expired from cache (2004) Unexceling (was I need a smart quote...) (1999) Success Stories (1997)