You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
11. How satisfied are you with YARP performance?
12. How satisfied are you with the YARP documentation?
13. How satisfied are you with the customizability of YARP?
14. How satisfied are you that YARP is ready for a 1.0 release?
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.
The text was updated successfully, but these errors were encountered: