![フロントエンド向けの API サーバリニューアルに GraphQL を検討している話 - エムスリーテックブログ](https://cdn-ak-scissors.b.st-hatena.com/image/square/874f33ff3af7174d8be40b638fa9a5c60be3d34b/height=288;version=1;width=512/https%3A%2F%2Fcdn-ak.f.st-hatena.com%2Fimages%2Ffotolife%2Fm%2Fma2gedev%2F20180703%2F20180703211931.png)
Logo from graph-gophersIn the beginning: Apollo ServerWhen it comes to building a graphQL server, almost everyone looks to Apollo Server; we were no different. Apollo allowed us to get a graphQL server up and running really quickly. We loved being able to return mock data almost instantly to our mobile/frontend engineers. Our graphQL server began to growAt SafetyCulture we have a microservice arch
Backend Engineer: Hmm. So you’re saying this “GraphQL” will allow any web or native engineer to arbitrarily query basically any field in any backend service, recursively, however they want, without any backend engineers involved? Frontend Engineer: Yeah, right? It’s amazing! […silence…] Backend Engineer: Guards, seize this person. For several years, we had a few eager advocates for GraphQL at Airb
Prisma provides the best experience for your team to work and interact with databases. Even complex things like connection pooling, caching, real-time database subscriptions are a breeze with our products. Build your application, fortify to make everything run smoothly, and grow with your users and requirements.
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く