Here’s what’s going on. Were adding a dependency management clause to allow us to bring in the spring cloud starters. Then we’re using the correct version of spring cloud so that it will be compatible with our spring boot version. Next, we’re adding feign client which will allow us to build a declarative rest client. Finally, we’re adding the fabric 8 framework that allows our spring boot application to interact with kubernetes.<\/p>\n\n\n\n
Create the REST Client<\/h2>\n\n\n\n
Create the following packages under src\/main\/java<\/code><\/p>\n\n\n\n
Now create a class called MessageResponseDTO <\/code>in com.bullyrooks.cloud_application.message_generator.client.dto<\/code> with this content:<\/p>\n\n\n\n
This will be the DTO that receives the response payload from the Message-generator service.<\/p>\n\n\n\n
Next make an interface <\/strong>called MessageGeneratorClient <\/code>in com.bullyrooks.cloud_application.message_generator.client<\/code>. Add this content<\/p>\n\n\n\n
Next, we need to enable the kubernetes and feign client functionality. Edit CloudApplication <\/code>in com.bullyrooks.cloud_application<\/code> and add these annotations<\/p>\n\n\n\n
@SpringBootApplication\r\n@<\/span>EnableDiscoveryClient\r\n@EnableFeignClients\r\npublic class CloudApplication {<\/code><\/pre>\n\n\n\n
Now we want to make sure that we can call the client from our service layer. Update MessageService <\/code>with this code<\/p>\n\n\n\n
Here we’ve added the autowire for the new client application as well as a call to the message generator service if a message was not passed in.<\/p>\n\n\n\n
Testing<\/h2>\n\n\n\n
Now we’ll update MessageControllerTest<\/code> to add some tests for the new behavior<\/p>\n\n\n\n
As you can see in this test, we’re not passing in a message <\/code>field in the body of the request. We’re also adding a mock that says when the feign client is called, return a new quote. Most of the rest should look familiar except, since we don’t know the message, we’re just testing if we got a non-null response back and confirm that the message that was returned is the same one that is stored in the database.<\/p>\n\n\n\n
Go ahead and run the test. It should pass.<\/p>\n\n\n\n
Commit and push<\/h2>\n\n\n\n
git add .\ngit commit -m \"retrieve message from message generator if missing\"\ngit push --set-upstream origin kube<\/code><\/pre>\n\n\n\n
This should successfully build on the feature branch. If it does, go ahead and merge to main to deploy it to okteto<\/p>\n\n\n\n
This should again successfully build and you should see it get deployed to okteto.<\/p>\n\n\n\n<\/figure>\n\n\n\n<\/figure>\n\n\n\n
Manual Test<\/h2>\n\n\n\n
Lets just double check with postman<\/p>\n\n\n\n<\/figure>\n\n\n\n
And confirm in the okteto logs<\/p>\n\n\n\n<\/figure>\n\n\n\n
Congratulations, you just got two microservices to communicate with each other in a cloud hosted kubernetes environment!<\/p>\n","protected":false},"excerpt":{"rendered":"
\nNow that we’ve got a new service, we’re going to make it…\n<\/div>\n
![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-1024x477.png?resize=960%2C447&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-1-1024x395.png?resize=960%2C370&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-2.png?resize=960%2C709&ssl=1\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-3-1024x117.png?resize=960%2C110&ssl=1\")
<\/figure>\n\n\n\n