Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Congratulations, schema changes are now directly visible outside your organization.

For some of our outgoing files at $employer, there's a notice period of... I think I remember it being 30 days for additional code values and 90 days for layout changes. That sort of planning ahead becomes much harder if every single schema change is immediately visible to outsiders.



API is just another schema. You can make a VIEW in SQL db to keep that VIEW schema stable, while changing the source schema without downtime.


That’s great for making db operations easier. Just because you make a pseudo-API out of a view doesn’t mean you should.

The problems are in the realm of non-functional requirements. Quotas, security, protocol support, asynchronous batch and bulk data access, granular access control, throttling…you can try to do this with your db, and many have, but the square peg will eventually not fit anymore.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: