Any constraints/risks to expose REST/GraphQL API for one docker service #1970
Unanswered
layfrank-xu
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
Currently one of our projects/docker-services is planning to support Reactive REST APIs along with existing GraphQL APIs.
Both REST and GraphQL will be built on Spring-Boot/Webflux stack.
Want to check here, are there any known constraints or potential risks in case there were already some teams tried with such mixed mode before?
Beta Was this translation helpful? Give feedback.
All reactions