I love NoSQL - itās lightening fast, but thereās a limit to what you can store in a key/value db. OK NoSQL is more than key/value pairs but at itās base itās simply that. The one I see as the most interesting is ObjectDBs which falls under the NoSQL non-relational DB orientation.
Blockchain databases are a really exciting concept also but require a precise idea and so not really open to the .io principle.
But yeah, cloud-based non-relational *SQL is definitely the way forward for db storage because the vast majority of todayās data (look at amazon outside of individual product details - they clearly use it) can be served from such resources, leaving the web frontend to be mega-responsive.
i wouldnt compare any nosql db to blockchain. in nosql theres no consens, no real distributed ledger, no pos/pow⦠and also data isnt immutable.
@George I just checked and played around some 5 minutes with restdb and this looks amazing. Quickly setup a DB within the cloud, easily define fields/relations and youre ready to go and query via json or similar. Also media is handled. This is just increcible powerful but Iām now confused where I should add wappler. Maybe with design and queries? Maybe all admin stuff or storing could be done with rest side like 0auth as I wrote in some posts before?
0Auth: Login/Userroles/Authentification
Restdb.io: Db hosting, db relation and Media handling/storing
Wappler: API Json Queries, design and some DB actions�
As told: Iām confused I wish Iāve never heard about that project
Going to buck a trend i think by this. Took a quick look at RestDB
Question: Why would a want to replace my proven, full featured, cloud hosted, industry standard MySql database functionality for a less functional NOSQL alternative and potentially pay $1,000s for the privilege?
I donāt think you should replace your perfectly working MySQL databases with NoSQL.
Relational databases are still perfect for storing tabular data, specially that needs lots of manipulations or calculations like financial data.
However document based and NoSQL databases are on the rise because of their much better storage and query of document/ objects with their properties also json support.
And that is why you also get those hybride databases as all major database providers add document/ object support to their existing databases.
As the browsers are getting more and more interactive and advanced, people can create extensive rich client applications and the role of the server side is becoming more or less just the data delivery.
That is why cloud databases are on the rise now as well. You donāt need much but a good database to serve your needs.
On the other side there is also a great development of the blockchain technology, serverless decentralized peer 2 peer data technology. Which also has a great place and purpose.
So you just have to pick the right technology that suits your needs the best.
Yes I accept that there may be places where this is relevant but I would suggest that 99% of the Wappler based development of data driven websites will probably be served by more traditional database platforms, not least until the high prices of alternatives drop.
I suspect we will see these new technologies appearing in the more common platforms, Microsoft are big on cloud now and I suspect MS SQL will lead but where it goes MySql will likely follow.
Seen too many new āinnovationsā come and go, i am more an āif it isnāt broke, donāt fix itā guy.
I have looked at the PHP MySQL API in the past but never saw a great need for it, perhaps now may be the time to look more closely into it.
I get how these platforms are very popular with some sections of developers, especially the Python community ( i love python but rarely actually use it in web development) who use value pairs like tuples and dictionaries all the time, just donāt see it as a must for a php/ jquery environment of Wappler.
But everyone to their own, horses for courses as they say,