RE: [WebDNA] NoSQL: sharing some ideas

This WebDNA talk-list message is from

2013

It keeps the original formatting. numero = 110954
interpreted = N
texte = Thank you so much for sharing. Never really looked at it that way. If onestored the file as XML or JSON and if I need "read and write" capability tothat file to update data and so forth ....how do you go about it?I know WebDNA has a XML interpreter but I have not really used it and as forJSON, there is no WebDNA interpreter. I would appreciate your thoughts onthis.Thanks ...Terry Nair-----Original Message-----From: christophe.billiottet@webdna.us[mailto:christophe.billiottet@webdna.us] Sent: Wednesday, December 04, 2013 19:02To: Subject: [WebDNA] NoSQL: sharing some ideasSharing some ideas.I was reading about NoSQL.Interactive applications have changed dramatically over the last 15 years,and so have the data management needs of those apps. Today, NoSQL isincreasingly considered a viable alternative to relational databases,especially as more organizations recognize that operating at scale is betterachieved on clusters of standard, commodity servers, and a schema-less datamodel is often better for the variety and type of data captured andprocessed today.Today, most new applications (both consumer and business) use a three-tierInternet architecture, run in a public or private cloud, and support largenumbers of users.At the database tier, relational databases were originally the popularchoice. Their use was increasingly problematic however, because they are acentralized, share-everything technology that scales up rather than out.This made them a poor fit for applications that require easy and dynamicscalability. NoSQL databases have been built from the ground up to bedistributed, scale-out technologies and therefore fit better with the highlydistributed nature of the three-tier Internet architecture.Relational and NoSQL data models are very different. The relational modeltakes data and separates it into many interrelated tables that contain rowsand columns. Tables reference each other through foreign keys that arestored in columns as well. When looking up data, the desired informationneeds to be collected from many tables (often hundreds in today's enterpriseapplications) and combined before it can be provided to the application.Similarly, when writing data, the write needs to be coordinated andperformed on many tables.WebDNA has all the tools to build basic NoSQL databases:[appendfile], [deletefile], [writefile], [createfolder], [include] etc...Basically, storing data in "NoSQL format" writes XML or JSON (or not)formatted files, one file per record. If the files are text files, then theyare fully transportable, whatever the platform, a cloud storage being ideal.WebDNA databases as we know them just record an index of these files and fewmore data, whatever we want, and the place of the file, whatever the disk,whatever the server. It is not even necessary to keep all the files on thesame server or in the same data center. It is fully scalable.I built my first NoSQL database in 2000 with WebDNA, without even knowinghow to name it. It was a invoicing system and customers had to be able torecover their invoices online. Invoices were just text files, included intoa design frame, with an index in a WebDNA database.As of today, the frame design changed, the platform changed three times andis now hosted in a cloud, and there are 385,962 invoices devided in about100 directories. WebDNA index keeps track of the files names and paths aswell as few other informations, but the WebDNA indexing database takes lessthan 13MB. Searching for an old invoice takes miliseconds. The cloud offershigh availability and load sharing.- chris Associated Messages, from the most recent to the oldest:

Re: [WebDNA] NoSQL: sharing some ideas (Terry Wilson 2013)
Re: [WebDNA] NoSQL: sharing some ideas (christophe.billiottet@webdna.us 2013)
RE: [WebDNA] NoSQL: sharing some ideas ("Terry Nair" 2013)

Thank you so much for sharing. Never really looked at it that way. If onestored the file as XML or JSON and if I need "read and write" capability tothat file to update data and so forth ....how do you go about it?I know WebDNA has a XML interpreter but I have not really used it and as forJSON, there is no WebDNA interpreter. I would appreciate your thoughts onthis.Thanks ...Terry Nair-----Original Message-----From: christophe.billiottet@webdna.us[mailto:christophe.billiottet@webdna.us] Sent: Wednesday, December 04, 2013 19:02To: Subject: [WebDNA] NoSQL: sharing some ideasSharing some ideas.I was reading about NoSQL.Interactive applications have changed dramatically over the last 15 years,and so have the data management needs of those apps. Today, NoSQL isincreasingly considered a viable alternative to relational databases,especially as more organizations recognize that operating at scale is betterachieved on clusters of standard, commodity servers, and a schema-less datamodel is often better for the variety and type of data captured andprocessed today.Today, most new applications (both consumer and business) use a three-tierInternet architecture, run in a public or private cloud, and support largenumbers of users.At the database tier, relational databases were originally the popularchoice. Their use was increasingly problematic however, because they are acentralized, share-everything technology that scales up rather than out.This made them a poor fit for applications that require easy and dynamicscalability. NoSQL databases have been built from the ground up to bedistributed, scale-out technologies and therefore fit better with the highlydistributed nature of the three-tier Internet architecture.Relational and NoSQL data models are very different. The relational modeltakes data and separates it into many interrelated tables that contain rowsand columns. Tables reference each other through foreign keys that arestored in columns as well. When looking up data, the desired informationneeds to be collected from many tables (often hundreds in today's enterpriseapplications) and combined before it can be provided to the application.Similarly, when writing data, the write needs to be coordinated andperformed on many tables.WebDNA has all the tools to build basic NoSQL databases:[appendfile], [deletefile], [writefile], [createfolder], [include] etc...Basically, storing data in "NoSQL format" writes XML or JSON (or not)formatted files, one file per record. If the files are text files, then theyare fully transportable, whatever the platform, a cloud storage being ideal.WebDNA databases as we know them just record an index of these files and fewmore data, whatever we want, and the place of the file, whatever the disk,whatever the server. It is not even necessary to keep all the files on thesame server or in the same data center. It is fully scalable.I built my first NoSQL database in 2000 with WebDNA, without even knowinghow to name it. It was a invoicing system and customers had to be able torecover their invoices online. Invoices were just text files, included intoa design frame, with an index in a WebDNA database.As of today, the frame design changed, the platform changed three times andis now hosted in a cloud, and there are 385,962 invoices devided in about100 directories. WebDNA index keeps track of the files names and paths aswell as few other informations, but the WebDNA indexing database takes lessthan 13MB. Searching for an old invoice takes miliseconds. The cloud offershigh availability and load sharing.- chris "Terry Nair"

DOWNLOAD WEBDNA NOW!

RE: [WebDNA] NoSQL: sharing some ideas

2013

Top Articles:

Related Readings: