5 ms·

What about DB (sql) access ? The 90% user case for any webservice today is : - parse request (ok) - issue a serie of DB requests <-- GO PAIN POINT - serializ

by bsaul 11y ago

What about DB (sql) access ? The 90% user case for any webservice today is : - parse request (ok) - issue a serie of DB requests <-- GO PAIN POINT - serialize result into either HTML (ok) or Json <-- PAIN POINT I'd say 2 pain points out of 3 is pretty bad IMHO. I would recommend go only for very specialized and technical web services, such as a websocket server. But really not for the average web developer task.

MoOmer 11y ago
Where are the pain points in DB requests or serialization? I've written several web apps with Go, and lots of ETL, and have yet to feel those as pain points.
- bsaul 11y ago
  Golang has nothing close to sqlalchemy, linq, activerecord or hibernate when it comes de querying a database. Last time i used go i had to write every single query and bind them manually to records in both ways. For writing simple api endpoints, this is really not up to today's standards.
  - MoOmer 11y ago
    Well, for one, ORM doesn't quite fit Go's philosophy, but there do exist some attempts to do this. For me, it's a non-issue, as it doesn't feel right with Go.
  - taternuts 11y ago
    That's really only a pain point for people who like ORMs. I personally prefer not to.
deleted 11y ago
[deleted]