this post was submitted on 19 Nov 2025
42 points (95.7% liked)
Programming
23542 readers
247 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's a good thought. It's a connection to one or more databases on their side, but it's read only. I suppose that's possible!
That’s if their API implementation itself is just bad and underlying DBs aren’t . If they or someone else with bad practices manages the DB you may be in worse situation than before. In general, to me, shared DB is bad because it is hard to not cut corners in such design and ensure that DB owner does not break contract for all consumers. This is basically why APIs created - to guarantee contracts and encapsulate change. But I digress. My point is that it will be your responsibility to ensure schema changes adopted to expected contract. If data is not normalized/structured, like say, it’s JSON then I would stay away.
I've no idea what's underneath, really. I'll ask and see what I learn.