3 ms·
Can you point us to the areas that you are looking for help on? If you save us work on looking for them and you might get a PR for your trouble.
by hcrean 4y ago
Can you point us to the areas that you are looking for help on? If you save us work on looking for them and you might get a PR for your trouble.
- asim 4y agoHey, I have a non-comprehensive list of issues for new services https://github.com/micro/services/issues https://github.com/micro/services/issues but most of the bugs/features are still in my head for other stuff. I think purely on the DB front we need to add a new Query endpoint that's more powerful that will accept a repeated array for Filter options that look like the below. message QueryRequest { repeated Filter filters = 1; } message QueryResponse { repeated Record records = 1; } message Filter { string field = 1; string op = 2; string value = 3; } Something like that. I think otherwise a majority of issues really become clear through use, so those using the services tend to see where the pitfalls are or where they can contribute. It's harder to do that without context and arguably less enjoyable for the person contributing as they're not seeing that change in whatever they're doing.
- cpursley 4y agoWhy not just use PostgREST for DB?
- asim 4y agoJust a desire to define an abstraction that's going to be consistent across all the services built. The value of a services catalog isn't just many separate services but the consistency and ability to reuse many in a coordinated fashion.
- ndriscoll 4y agoWhy would I use this instead of just using e.g. a postgres jdbc driver? How would I use this? A query compiler library (or service)? How do you do a join? Group by? CTEs? Window functions? Transactions? Bulk inserts/updates? Index and constraint management? Temporary tables? Why does the read endpoint have a hard limit?