-
Notifications
You must be signed in to change notification settings - Fork 88
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
Introduction to GRPC blog #239
base: master
Are you sure you want to change the base?
Conversation
reference. You can find on the application available on repository, shared on this article, some additional configurations | ||
related to the familiar spring patterns. Among other things, we have a `@Configuration` class which is used to configure | ||
our gRPC server to be running inside our spring application. In this configuratioon, `DerivativeCalculatorService` | ||
houses our previously shown derivative logic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reference. You can find on the application available on repository, shared on this article, some additional configurations | |
related to the familiar spring patterns. Among other things, we have a `@Configuration` class which is used to configure | |
our gRPC server to be running inside our spring application. In this configuratioon, `DerivativeCalculatorService` | |
houses our previously shown derivative logic. | |
reference. You can find in the application available on the repository and shared in this article some additional configurations related to the familiar spring patterns. Among other things, we have a `@Configuration` class to configure our gRPC server to run inside our spring application. In this configuration, `DerivativeCalculatorService` houses our previously shown derivative logic. |
Feel free to play around with the example and try other simple polynomials. Some caveats when using this, be aware that | ||
some requirements exist, for one, our polynomials we send include all exponents and coefficients (even 1 and 0), and | ||
that’s why we see `1x^1 + 1x^0` instead of `x + 1`, this is simply due to our simple parsing of the string polynomial. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to play around with the example and try other simple polynomials. Some caveats when using this, be aware that | |
some requirements exist, for one, our polynomials we send include all exponents and coefficients (even 1 and 0), and | |
that’s why we see `1x^1 + 1x^0` instead of `x + 1`, this is simply due to our simple parsing of the string polynomial. | |
Feel free to play around with the example and try other simple polynomials. Some caveats when using this, be aware that the polynomials we send to the server must include all exponents and coefficients (even 1 and 0), and | |
that’s why we see `1x^1 + 1x^0` instead of `x + 1`. This is simply due to our simple parsing of the string polynomial. |
|
||
We’ve now completed our simple GRPC example, this has a small protobuf definition, but these can be much more complex, | ||
if needed. We also created a simple docker configuration to get everything running locally and communication between | ||
the service and client. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a conclusion and call to action pls! This was a really fun exercise to read about!
It seems like we have two simple ways to represent the polynomial, a naive way (which we handle in our rest | ||
call) to do this is by sending it as a raw string. While this works, it could be cumbersome, as we will |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 simple ways... maybe state what they are first then go into the details?
No description provided.