This is useful. But you can achieve the same results in just a few more steps with Hasura or Supabase and end up with something that is close to production ready.
Show HN: Caffeine – Minimum viable back end for prototyping
11–20 of 83 posts
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#12Like the idea. Any user auth?
I wonder if parse is still around and supported? I thought that was pretty good for this kinda thing.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#13Nice to see that the interface for the DB was separated out:
https://github.com/rehacktive/caffeine/blob/master/service/s...
It's not "MVP" fashion but even for only one implementation making these interfaces is critical IMO.
That said, if it's not too much maybe consider adding a SQLite backend! :)
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#14Nice to see that the interface for the DB was separated out: https://github.com/rehacktive/caffeine/blob/master/service/s... It's not "MVP" fashion but even for only one implementation making these interfaces is critical IMO. That said, if it's not too much maybe consider adding a SQLite backend! :)
the SQLite implementation is in TODO :)
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#15This is useful. But you can achieve the same results in just a few more steps with Hasura or Supabase and end up with something that is close to production ready.
[deleted]
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#16A 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 container
Just a heads-up, you might want to take down the example website. Now that it's been posted to HN you might see malicious actors.
I also think it's prone to SQL injection at the moment? At least, it's raising a syntax error when inputting an apostrophe.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#17Feature 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?
SQLite could also be a good option
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#18Like the idea. Any user auth? I wonder if parse is still around and supported? I thought that was pretty good for this kinda thing.
Parse is still around and supported: https://github.com/parse-community/parse-server
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#19Like the idea. Any user auth? I wonder if parse is still around and supported? I thought that was pretty good for this kinda thing.
If you mean https://parseplatform.org/ then it looks to be still around.
Re: Show HN: Caffeine – Minimum viable back end for prototyping
#20FYI, there is a name clash with Caffeine, a Mac OS menu bar app that keeps the screen awake: https://intelliscapesolutions.com/apps/caffeine . But I guess this is expected with a name like this, and the scopes of the projects are clearly different, so this should be relatively harmless.