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

> doesn't push her to make unneccessary database calls for each request when business logic becomes significantly complex.

Are you objecting to holding all state in a database, or something else? If so, the only real alternative is to have individual servers hold state, which seems like a poor choice; one way or another you're going to hit the CAP theorem, and databases are well-optimized for getting you the best results from CAP that you're going to.



Absolutely not. On the contrary, I'm one of those developers who prefer to do things in SQL rather than application logic.




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

Search: