Re: [WebDNA] NoSQL: sharing some ideas

This WebDNA talk-list message is from

2013

It keeps the original formatting. numero = 110956
interpreted = N
texte = This sounds similar to the WebDNA cart system, with the individual =20files.On Dec 4, 2013, at 3:02 AM, christophe.billiottet@webdna.us wrote:> Sharing some ideas=85>> I was reading about NoSQL.>> Interactive applications have changed dramatically over the last 15 =20=> years, and so have the data management needs of those apps. Today, =20> NoSQL is increasingly considered a viable alternative to relational =20=> databases, especially as more organizations recognize that operating =20=> at scale is better achieved on clusters of standard, commodity =20> servers, and a schema-less data model is often better for the =20> variety and type of data captured and processed today.>> Today, most new applications (both consumer and business) use a =20> three-tier Internet architecture, run in a public or private cloud, =20=> and support large numbers of users.>> At the database tier, relational databases were originally the =20> popular choice. Their use was increasingly problematic however, =20> because they are a centralized, share-everything technology that =20> scales up rather than out. This made them a poor fit for =20> applications that require easy and dynamic scalability. NoSQL =20> databases have been built from the ground up to be distributed, =20> scale-out technologies and therefore fit better with the highly =20> distributed nature of the three-tier Internet architecture.>> Relational and NoSQL data models are very different. The relational =20=> model takes data and separates it into many interrelated tables that =20=> contain rows and columns. Tables reference each other through =20> foreign keys that are stored in columns as well. When looking up =20> data, the desired information needs to be collected from many tables =20=> (often hundreds in today=92s enterprise applications) and combined =20> before it can be provided to the application. Similarly, when =20> writing data, the write needs to be coordinated and performed on =20> many tables.>>>>> WebDNA has all the tools to build basic NoSQL databases:>> [appendfile], [deletefile], [writefile], [createfolder], [include] =20> etc...>> Basically, storing data in "NoSQL format" writes XML or JSON (or =20> not) formatted files, one file per record. If the files are text =20> files, then they are fully transportable, whatever the platform, a =20> cloud storage being ideal. WebDNA databases as we know them just =20> record an index of these files and few more data, whatever we want, =20=> and the place of the file, whatever the disk, whatever the server. =20> It is not even necessary to keep all the files on the same server or =20=> in the same data center. It is fully scalable.>> I built my first NoSQL database in 2000 with WebDNA, without even =20> knowing how to name it. It was a invoicing system and customers had =20=> to be able to recover their invoices online. Invoices were just text =20=> files, included into a design frame, with an index in a WebDNA =20> database.>> As of today, the frame design changed, the platform changed three =20> times and is now hosted in a cloud, and there are 385,962 invoices =20> devided in about 100 directories. WebDNA index keeps track of the =20> files names and paths as well as few other informations, but the =20> WebDNA indexing database takes less than 13MB. Searching for an old =20=> invoice takes miliseconds. The cloud offers high availability and =20> load sharing=85>> - 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)
[WebDNA] NoSQL: sharing some ideas (christophe.billiottet@webdna.us 2013)

This sounds similar to the WebDNA cart system, with the individual =20files.On Dec 4, 2013, at 3:02 AM, christophe.billiottet@webdna.us wrote:> Sharing some ideas=85>> I was reading about NoSQL.>> Interactive applications have changed dramatically over the last 15 =20=> years, and so have the data management needs of those apps. Today, =20> NoSQL is increasingly considered a viable alternative to relational =20=> databases, especially as more organizations recognize that operating =20=> at scale is better achieved on clusters of standard, commodity =20> servers, and a schema-less data model is often better for the =20> variety and type of data captured and processed today.>> Today, most new applications (both consumer and business) use a =20> three-tier Internet architecture, run in a public or private cloud, =20=> and support large numbers of users.>> At the database tier, relational databases were originally the =20> popular choice. Their use was increasingly problematic however, =20> because they are a centralized, share-everything technology that =20> scales up rather than out. This made them a poor fit for =20> applications that require easy and dynamic scalability. NoSQL =20> databases have been built from the ground up to be distributed, =20> scale-out technologies and therefore fit better with the highly =20> distributed nature of the three-tier Internet architecture.>> Relational and NoSQL data models are very different. The relational =20=> model takes data and separates it into many interrelated tables that =20=> contain rows and columns. Tables reference each other through =20> foreign keys that are stored in columns as well. When looking up =20> data, the desired information needs to be collected from many tables =20=> (often hundreds in today=92s enterprise applications) and combined =20> before it can be provided to the application. Similarly, when =20> writing data, the write needs to be coordinated and performed on =20> many tables.>>>>> WebDNA has all the tools to build basic NoSQL databases:>> [appendfile], [deletefile], [writefile], [createfolder], [include] =20> etc...>> Basically, storing data in "NoSQL format" writes XML or JSON (or =20> not) formatted files, one file per record. If the files are text =20> files, then they are fully transportable, whatever the platform, a =20> cloud storage being ideal. WebDNA databases as we know them just =20> record an index of these files and few more data, whatever we want, =20=> and the place of the file, whatever the disk, whatever the server. =20> It is not even necessary to keep all the files on the same server or =20=> in the same data center. It is fully scalable.>> I built my first NoSQL database in 2000 with WebDNA, without even =20> knowing how to name it. It was a invoicing system and customers had =20=> to be able to recover their invoices online. Invoices were just text =20=> files, included into a design frame, with an index in a WebDNA =20> database.>> As of today, the frame design changed, the platform changed three =20> times and is now hosted in a cloud, and there are 385,962 invoices =20> devided in about 100 directories. WebDNA index keeps track of the =20> files names and paths as well as few other informations, but the =20> WebDNA indexing database takes less than 13MB. Searching for an old =20=> invoice takes miliseconds. The cloud offers high availability and =20> load sharing=85>> - chris>> Terry Wilson

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] NoSQL: sharing some ideas

2013

Top Articles:

Related Readings: