[Ask IH] Simple JSON store in the cloud?
I have a need for a simple way to store JSON objects in the cloud to be retrieved programmatically. Is there a good solution for this?
My use case is this - I want to build my personal CV page. Instead of a dumb html page, I want to make the page dynamic so if I add any new work experience details to the backend, the CV page should show that.
I don't want to use a db which feels like an overkill. All I want to do is to store JSON objects/files somewhere and use them in my code.
Not dynamic, but this sounds like a job for a static site generator. IIRC jekyll and others support JSON as data source. Store on github, publish on netlify.
I've used Jekyll and static site gens in the past. Generating and regenerating sites locally feels like an overkill for some of use cases plus the entire setup feels very fragile and non-portable. E.g., if I am not at my device, I can't regenerate the site. I can't do it from my mobile.
Example use cases where static sites aren't going to cut it:
say I have an online bookshelf where I add books I recently read. Every time I finish a book, I have to regenerate the site which feels like a chore, something I'm likely to eventually stop doing.
online cv: say I finish a certification exam and want to add it to my online cv. It happens rarely enough that I'd have probably forgotten how to regenerate my site...so I have to spend some cycles relearning how to do that. Again, cumbersome and error prone.
A few more ideas to ponder:
Re 1. Sounds like you either are a good case for goodreads.com or similar or actually any blog software out there. Let somebody else take care of, just log in and update.
Re 2. How often do you update your CV? If you easily forget how stuff works, well, write a README.md. That's what I do because I tend to forget this stuff as well :)
If you don't want to do stuff yourself and just need something super simple, maybe check out very nice page builders, like https://carrd.co/ (very simple) or https://versoly.com/ (if you want it to be more).
Either way, you'll eventually have to compromise on something.
Pretty much this.
The tool I am developing sounds really close to what you are looking for. You can either manually edit your static JSON through the GUI or store it on GitHub and it will be updated on push: Mocki.io
You can use S3 for this.
You can put json files on most shared hosting accounts. No "cloud" needed. Even dropbox would do. Or github/gitlab.
Don't think I can easily write back (programmatically) to dropbox/drive without significant overhead. Plus, doesn't Drive (and Dropbox?) recommend against using their links to serve website content?
This comment was deleted 4 years ago
Few reasons....
some of my use cases don't need a db. See use cases listed here.
cost and complexity - how do I protect my db instance? does my use case justify the monthly spend?
easier to MVP with json than with a db - this is probably the main reason. I find it easier to mvp something using json files instead of setting up a well designed relational DB or breaking my head over shard/partitions of the NoSQL world
Read the use-case and think you're probably over-complicating your site. If you're creating a CV, you don't need a back-end at all.
You can have your website read from a Javascript json object, which you store in a .js file (just like any other code on the website).
This comment was deleted 4 years ago
This comment was deleted 4 years ago