sudowing

4 ms·

1.
by sudowing 4y ago
Indeed. Thats actually how my team's FE engineers called our API. But once other teams started integrating -- we heard all kinds of feedback. My thoughts afterward were simply that people under the time pressure to push features daily
2.
by sudowing 4y ago
"... rough edges ... complex" I've put a couple GraphQL services into production and have similar thoughts. What suprised me most were the range of views from colleagues when they needed to integrate into one of their product
3.
by sudowing 4y ago
I published an app via docker that can be used for db migrations with all dbs supported by knex.js I'm pretty sure the core migration functionality provided by knex is supported -- along with some project specific features which suppor
4.
by sudowing 5y ago
I spent a much of 2020 developing a project that auto provisions REST, GraphQL & gRPC services that support CRUD operations (with full validation) to tables, views and materialized views of several popular databases (postgres, postgis,
5.
by sudowing 6y ago
I can't say I reached any conclusions -- I can only offer that the handful of people that have offered feedback found if feature rich and easy to use.
6.
by sudowing 6y ago
The `versus` nature of this question was the driving force behind a project I built last year. I've been in multiple shops where REST was the standard -- and while folks had interest in exploring GraphQL or gRPC, we could not justify p
7.
SHOW HN: REST, GraphQL and gRPC Services via NPM or Docker
4 points by sudowing 6y ago|0 comments