4 ms·
Yeah, I was thinking of using mysql+nosql. RethinkDb was my main choice, but I'd rather have someone take care of the backend for me like a DAAS, mostly to alle
by kevindeasis 10y ago
Yeah, I was thinking of using mysql+nosql. RethinkDb was my main choice, but I'd rather have someone take care of the backend for me like a DAAS, mostly to alleviate the pain of doing a project solo, but compose seems too expensive to use to prototype some ideas.
- tracker1 10y agoAgreed, if you don't mind getting locked into a platform, AWS, Azure, and Google all have options for varying no-sql/search and/or big-table data stores... but ymmv there.
- kevindeasis 10y agoI hear ya! I'm ultimately going to go with the strategy that you've mentioned. NoSql+Sql with Google and just write my ORMs and wrappers. Thanks for the advice!