|
|
|
|
|
|
by gcoda
2622 days ago
|
|
|
I got lots of question, got bit excited while glancing thru docs. What is the minimal system requirements?
And what about partitioning, replication, event log, etc. Is there a native way hook to graphql resolvers?
I really like it either way, there some tools for composing and stitching schemas. plans for hosted and managed solution? Did you consider "pageInfo" type, maybe it is just me, but it proved very useful on frontend. instead of `Movies: [Movie]` Movies {
pageInfo: PageInfo # { hasNextPage, endCursor }
nodes: [Movie]
}
|
|
|
Minimal requirements are similar to that of PostgreSQL. EdgeDB should run comfortably on an average server.
> And what about partitioning, replication, event log, etc.
Tooling for that will be coming in the next few alpha releases.
> Is there a native way hook to graphql resolvers? I really like it either way, there some tools for composing and stitching schemas.
Not right now. Although I think it should be possible to do what you want via one of the existing GraphQL proxies, like Apollo.
> plans for hosted and managed solution?
Yes, but no ETA right now. This is one of our highest priorities.
> Did you consider "pageInfo" type, maybe it is just me, but it proved very useful on frontend.
We can add that. One of the first-priority things on our list w.r.t. GraphQL though is to implement Database Views, which will allow selectively exposing your schema (and controlling how it is exposed).