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

Ah yes. That is brilliant until it isn't. For any reasonably complex business problem you will run into:

* Performance issues: table scans, high memory usage for joins, crazy sql execution plans, lock contention

* Security problems: especially around authorisation. Who can see what data. You'll start to need rules engines written as stored procedure or some shit.

* Business logic: can a SQL work out the country city, state and federal tax for the address? Maybe it can. Maybe that query will grind the system to a halt. Maybe you'll slap redis and 1000 sql replications. Maybe you are no longer just doing SQL!

Yeah fortunately for all of us shit is complicated and needs bespoke thinking to solve each problem.

There are problems where your ideas work well (typically consumer facing startup types who can rewrite when they raise a bit more money).

If that is how you do things I know the conversations you'll be having next year already. And that is from just ORM abuse not even front end SQL.

I tried to use Firebase in earnest which is the ultimate in that approach and it is awful. You hit a bunch of new and worse problems because you don't want anything to do with an EC2.



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

Search: