[S2GRAPH-248] I made the first commit for the issue.
Link: https://github.com/daewon/incubator-s2graph/tree/S2GRAPH-248/s2http
I chose `akka http` because it was stable and lightweight with the`
framework` for `http layer`.
The initial implementation focused on minimizing external dependencies
No problem deawon, I will work on S2GRAPH-249 based on your commit.
Just quick questions, I guess you mention 4 high-level functionalities.
1. write
2. read
3. admin
4. graphql
It seems like you intend to migrate s2graphql also into this new subproject
s2http, so just quick question, are we
@DOYUNG
Thank you for your feedback.
I think the graphql project does not need to have an http layer.
Therefore, in the s2graphql project, i want to remove the http layer by
leaving only graphql's unique functions such as schema creation and query
parsing.
I will also be able to set the
