Re:Etcd, or, why modern software makes me sad
by say-vagnes on Tuesday July 14, 2020 @08:34PM
(#23839866)
I feel like GraphQL is the new NoSQL. Not just that it's mistakenly adopted, but also that it is quite valuable for the right use cases, but the public doesn't seem to understand what those are.
Do you really, _really_ need to support queries? 99/100, I'd guess no, and thus constraining people to a more defined interface and access pattern is simpler.
Re:Etcd, or, why modern software makes me sad
by what-the-grump on Friday July 17, 2020 @03:15AM
(#23868016)
Oh... you need to fill your RDMS with a bunch of JSON responses from your 3rd party API. So you can then decode them in memory because I actually need to select * where identifier = 'banana' to do analytics.
Meanwhile the API returns highly structured data perfect for a RDMS, but we dont know how to query SQL without an API in the frontend. So welcome to my hell.
Re:Etcd, or, why modern software makes me sad
by Nextgrid on Tuesday July 14, 2020 @09:00PM
(#23840054)
It's a combination of resume-driven development and premature optimization.
The former doesn't need explaining but the latter can be explained as developers being concerned about requiring the benefits of GraphQL in some uncertain future and decide to include it from the start, even though in most cases they end up never actually reaping the benefits while still being plagued by the extra overhead of using that technology.
I'm a bit confused as to how it's become so popular for normal development when it seems to have a lot more boilerplate and setup than a simple REST API.