4 ms·
A variation on this would be to put the database behind a service that abstracted over the schema, though that only works for basic CRUD queries and not complex
by rdnetto 9y ago
A variation on this would be to put the database behind a service that abstracted over the schema, though that only works for basic CRUD queries and not complex aggregations. This service would probably evolve from the monolith.
- deleted 9y ago[deleted]
- collyw 9y agoYou mean like an API?
- Olivia4654 9y agoI get paid over $95 per hour working from home with 2 kids at home. I never thought I'd be able to do it but my best friend earns over 10k a month doing this and she convinced me to try. The potential with this is endless. Heres what I've been doing, •••••••••>>http://www.joinmate2.com http://www.joinmate2.com
- rhizome 9y agoIt sounds like you're describing ORM-as-API. Which, if you find you need it, great, but I wouldn't try to fool myself that introducing a mediating process like that is all that different from what the language/framework likely already provides (contemporary development frameworks are common). It's just ("just") abstracted to operate on network basis. Actually, what you describe sounds like a reduction in functionality from a non-API model. Hopefully that parses as English, it's still morning for me.