can we use JSON as a database?

Question

I'm looking for fast and efficient data storage to build my PHP based web site. I'm aware of MySql. Can I use a JSON file in my server root directory instead of a MySQL database? If yes, what is the best way to do it?

Answer 1

One obvious case when you can prefer JSON (or another file format) over database is when all yours (relatively small) data stored in the application cache.

When an application server (re)starts, an application reads data from file(s) and stores it in the data structure.

When data changes, an application updates file(s).

Advantage: no database.

Disadvantage: for a number of reasons can be used only for systems with relatively small data. For example, a very specific product site with several hundreds of products.

Answer 2

I wrote an Object Document Mapper to use with json files called JSON ODM may be a bit late, but if it is still needed it is open source under MIT Licence.

It provides a query languge, and some GeoJSON tools

Answer 3

The new version of IBM Informix 12.10 xC2 supports now JSON.
check the link : http://pic.dhe.ibm.com/infocenter/informix/v121/topic/com.ibm.json.doc/ids_json_007.htm

The manual says it is compatible with MongoDB drivers.

About the Informix JSON compatibility

Applications that use the JSON-oriented query language, created by MongoDB, can interact with data stored in Informix® databases. The Informix database server also provides built-in JSON and BSON (binary JSON) data types.

You can use MongoDB community drivers to insert, update, and query JSON documents in Informix.

Not sure, but I believe you can use the Innovator-C edition (free for production) to test and use it with no-cost either for production enviroment.

Answer 4

You can use any single file, including a JSON file, like this:

• Lock it somehow (google PHP file locking, it's possibly as simple as adding a parameter to file open function or changing function name to locking version).

• Read the data from file and parse it to internal data stucture.

• Optionally modify the data in internal data structure.

• If you modified the data, truncate the file to 0 length and write new data to it.

• Unlock the file as soon as you can, other requests may be waiting...

• You can keep using the data in internal structures to render the page, just remember it may be out-dated as soon as you release the file lock and other HTTP request can modify it.

Also, if you modify the data from user's web form, remember that it may have been modified in between. Like, load page with user details for editing, then other user deletes that user, then editer tries to save the changed details, and should probably get error instead of re-creating deleted user.

Note: This is very inefficient. If you are building a site where you expect more than say 10 simultaneous users, you have to use a more sophisticated scheme, or just use existing database... Also, you can't have too much data, because parsing JSON and generating modified JSON takes time.

As long as you have just one user at a time, it'll just get slower and slower as amount of data grows, but as user count increases, and more users means both more requests and more data, things start to get exponentially slower and you very soon hit limit where HTTP requests start to expire before file is available for handling the request...

At that point, do not try to hack it to make it faster, but instead pick some existing database framework (SQL or nosql or file-based). If you start hacking together your own, you just end up re-inventing the wheel, usually poorly :-). Well, unless it is just programming exercise, but even then it might be better to instead learn use of some existing framework.