Show HN: Caffeine – Minimum viable back end for prototyping
1–10 of 83 posts
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#2A very basic REST service for JSON data - enough for prototyping and MVPs!
Features:
no need to set up a database, all data is managed automagically*
REST paradigm CRUD for multiple entities/namespaces
schema validation
search using jq like syntax
CORS enabled
easy to deploy as containerRe: Show HN: Caffeine – Minimum viable back end for prototyping
#3Very nice idea! I haven't seen anything like it.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#4This may become very useful! I will definitely check it out.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#5Cool! I like that it's zero config to start with, and that adding schemas can itself just be done with a request.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#6Feature request: supply .json file via command line to pre-load data into the in-memory database.
Taking it even further; how about persisting the data in the file?
Sometimes your prototype will need some pre-added data so I think this might be useful.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#7Feature request: supply .json file via command line to pre-load data into the in-memory database. Taking it even further; how about persisting the data in the file? Sometimes your prototype will need some pre-added data so I think this might be useful.
My first thought too, but I guess it's also very easy to hand-roll an init_data.sh script with a bunch of POST curls to populate the DB.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#8Feature request: supply .json file via command line to pre-load data into the in-memory database. Taking it even further; how about persisting the data in the file? Sometimes your prototype will need some pre-added data so I think this might be useful.
Can probably do that with some `jq` and CURL magic already!
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#9Feature request: supply .json file via command line to pre-load data into the in-memory database. Taking it even further; how about persisting the data in the file? Sometimes your prototype will need some pre-added data so I think this might be useful.
currently there are two implementation for the database "behind": in memory or with postgres, both with zero config (except for starting an instance of postgres, in the second case!).
it can be easily extended to use files as persistence, good idea :)
regarding the pre-population, you can just make a quick script with curl that will add some data after you run the service. any thought?
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#10Feature request: supply .json file via command line to pre-load data into the in-memory database. Taking it even further; how about persisting the data in the file? Sometimes your prototype will need some pre-added data so I think this might be useful.
My first thought too, but I guess it's also very easy to hand-roll an init_data.sh script with a bunch of POST curls to populate the DB.
exactly!