Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

YARP Feedback Wanted [April 2021] #916

Closed
samsp-msft opened this issue Apr 15, 2021 · 1 comment
Closed

YARP Feedback Wanted [April 2021] #916

samsp-msft opened this issue Apr 15, 2021 · 1 comment
Milestone

Comments

@samsp-msft
Copy link
Member

samsp-msft commented Apr 15, 2021

YARP Feedback

We think we are pretty close to what we think should be in the feature set for YARP 1.0, and have been doing some code reviews to clean up the API and get ready to declare YARP ready for a 1.0 release. But we'd like to hear your feedback on how well YARP meets your needs, and if not what is missing or broken for you?

If you are using YARP or investigating it, please tell us about your experiences. As reporting this kind of info in issues doesn't work well, please send your answers to [email protected].

YARP Survey

1. What stage are you at with your YARP deployment?

Investigating | Deployed | Rejected | Blocked | Other

Please provide more details for Rejected, Blocked or Other

If you have deployed YARP :-

2. How many instances are deployed?

3. Approximately what hardware is it deployed on?

CPU core count & memory. If cloud hosted, which VM size

4. What's your typical daily peak RPS?

5. How many routes/clusters/destinations do you have configured?

If you have deployed or are planning a deployment :-

6. Is your configuration from a file or dynamic through code?

7. What customizations have you made, or are planning to YARP?

8. How easy did you find the customization process?

9. What if anything is missing from YARP?

Overall impressions :-

10. How satisfied are you with YARP, is it meeting your needs?

Very Unsatisfied Unsatisfied Meh Satisfied Very Satisfied
[ ] [ ] [ ] [ ] [ ]

11. How satisfied are you with YARP performance?

Very Unsatisfied Unsatisfied Meh Satisfied Very Satisfied N/A
[ ] [ ] [ ] [ ] [ ] [ ]

12. How satisfied are you with the YARP documentation?

Very Unsatisfied Unsatisfied Meh Satisfied Very Satisfied N/A
[ ] [ ] [ ] [ ] [ ] [ ]

13. How satisfied are you with the customizability of YARP?

Very Unsatisfied Unsatisfied Meh Satisfied Very Satisfied N/A
[ ] [ ] [ ] [ ] [ ] [ ]

14. How satisfied are you that YARP is ready for a 1.0 release?

Very Unsatisfied Unsatisfied Meh Satisfied Very Satisfied N/A
[ ] [ ] [ ] [ ] [ ] [ ]

About You :-

15. (optional) Who are you? What is your github alias?

16. (optional) What organization are you using YARP for?

17. (optional) If you would be prepared to talk more with the YARP engineering team, please provide contact details?

Finally :-

18. Any other feedback you'd like to provide?

Thankyou,

@samsp-mstf on behalf of the YARP team.

@dotnet dotnet locked and limited conversation to collaborators Apr 15, 2021
@samsp-msft samsp-msft pinned this issue Apr 15, 2021
@karelz karelz added this to the YARP 1.0.0 milestone Apr 22, 2021
@samsp-msft samsp-msft unpinned this issue Sep 16, 2021
@samsp-msft samsp-msft modified the milestones: YARP 1.0.0, Backlog Sep 16, 2021
@samsp-msft
Copy link
Member Author

Closing as we have now shipped V1 of YARP. We still welcome feedback, but keeping this issue open doesn't really make sense.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants