{"id":1356,"date":"2022-02-27T19:56:41","date_gmt":"2022-02-28T02:56:41","guid":{"rendered":"https:\/\/bullyrooks.com\/?p=1356"},"modified":"2022-02-27T19:57:25","modified_gmt":"2022-02-28T02:57:25","slug":"kube-cloud-pt5-create-an-event-consumer","status":"publish","type":"post","link":"https:\/\/bullyrooks.com\/index.php\/2022\/02\/27\/kube-cloud-pt5-create-an-event-consumer\/","title":{"rendered":"Kube Cloud Pt5 | Create an Event Consumer"},"content":{"rendered":"\n

Now that we’ve got messages being published to kafka, we are going to need to build our consumer that receives those events and stores them into the mongo database.<\/p>\n\n\n\n

Go ahead and create a new repository called message-repository according to the microservice startup course here<\/a>. <\/p>\n\n\n\n

This is the pom.xml that we’ll need:<\/p>\n\n\n\n

<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<project xmlns=\"http:\/\/maven.apache.org\/POM\/4.0.0\" xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance\"\n\txsi:schemaLocation=\"http:\/\/maven.apache.org\/POM\/4.0.0 https:\/\/maven.apache.org\/xsd\/maven-4.0.0.xsd\">\n\t<modelVersion>4.0.0<\/modelVersion>\n\t<parent>\n\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t<artifactId>spring-boot-starter-parent<\/artifactId>\n\t\t<version>2.6.3<\/version>\n\t\t<relativePath\/> <!-- lookup parent from repository -->\n\t<\/parent>\n\t<groupId>com.bullyrooks<\/groupId>\n\t<artifactId>message-repository<\/artifactId>\n\t<version>0.0.1-SNAPSHOT<\/version>\n\t<name>message-repository<\/name>\n\t<description>Stores messages<\/description>\n\t<properties>\n\t\t<java.version>11<\/java.version>\n\t\t<spring-cloud.version>2021.0.1<\/spring-cloud.version>\n\t\t<org.mapstruct.version>1.4.2.Final<\/org.mapstruct.version>\n\t\t<logstash-logback-encoder.version>6.4<\/logstash-logback-encoder.version>\n\t\t<log4j2.version>2.17.1<\/log4j2.version>\n\t\t<logzio-logback-appender.version>v1.0.25<\/logzio-logback-appender.version>\n\t\t<micrometer-registry-logzio.version>1.0.2<\/micrometer-registry-logzio.version>\n\t\t<javafaker.version>1.0.2<\/javafaker.version>\n\t<\/properties>\n\t<dependencies>\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-starter-web<\/artifactId>\n\t\t<\/dependency>\n\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-starter-data-mongodb<\/artifactId>\n\t\t<\/dependency>\n\t\t<!-- Streams and Kafka -->\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.cloud<\/groupId>\n\t\t\t<artifactId>spring-cloud-stream<\/artifactId>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.cloud<\/groupId>\n\t\t\t<artifactId>spring-cloud-stream-binder-kafka<\/artifactId>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.cloud<\/groupId>\n\t\t\t<artifactId>spring-cloud-stream<\/artifactId>\n\t\t\t<type>test-jar<\/type>\n\t\t\t<classifier>test-binder<\/classifier>\n\t\t\t<scope>test<\/scope>\n\t\t<\/dependency>\n\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-devtools<\/artifactId>\n\t\t\t<scope>runtime<\/scope>\n\t\t\t<optional>true<\/optional>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.projectlombok<\/groupId>\n\t\t\t<artifactId>lombok<\/artifactId>\n\t\t\t<optional>true<\/optional>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-starter-test<\/artifactId>\n\t\t\t<scope>test<\/scope>\n\t\t<\/dependency>\n\n\n\t\t<!-- Health Checks and Metrics -->\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-starter-actuator<\/artifactId>\n\t\t<\/dependency>\n\n\t\t<!-- mapstruct -->\n\t\t<dependency>\n\t\t\t<groupId>org.mapstruct<\/groupId>\n\t\t\t<artifactId>mapstruct<\/artifactId>\n\t\t\t<version>${org.mapstruct.version}<\/version>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.mapstruct<\/groupId>\n\t\t\t<artifactId>mapstruct-processor<\/artifactId>\n\t\t\t<version>${org.mapstruct.version}<\/version>\n\t\t<\/dependency>\n\n\t\t<!-- logging -->\n\t\t<dependency>\n\t\t\t<groupId>net.logstash.logback<\/groupId>\n\t\t\t<artifactId>logstash-logback-encoder<\/artifactId>\n\t\t\t<version>${logstash-logback-encoder.version}<\/version>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>io.logz.logback<\/groupId>\n\t\t\t<artifactId>logzio-logback-appender<\/artifactId>\n\t\t\t<version>${logzio-logback-appender.version}<\/version>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t<artifactId>spring-boot-starter-aop<\/artifactId>\n\t\t<\/dependency>\n\t\t<dependency>\n\t\t\t<groupId>io.logz.micrometer<\/groupId>\n\t\t\t<artifactId>micrometer-registry-logzio<\/artifactId>\n\t\t\t<version>${micrometer-registry-logzio.version}<\/version>\n\t\t<\/dependency>\n\n\t\t<dependency>\n\t\t\t<groupId>com.github.javafaker<\/groupId>\n\t\t\t<artifactId>javafaker<\/artifactId>\n\t\t\t<version>${javafaker.version}<\/version>\n\t\t<\/dependency>\n\n\t\t<dependency>\n\t\t\t<groupId>de.flapdoodle.embed<\/groupId>\n\t\t\t<artifactId>de.flapdoodle.embed.mongo<\/artifactId>\n\t\t\t<scope>test<\/scope>\n\t\t<\/dependency>\n\n\t<\/dependencies>\n\t<dependencyManagement>\n\t\t<dependencies>\n\t\t\t<dependency>\n\t\t\t\t<groupId>org.springframework.cloud<\/groupId>\n\t\t\t\t<artifactId>spring-cloud-dependencies<\/artifactId>\n\t\t\t\t<version>${spring-cloud.version}<\/version>\n\t\t\t\t<type>pom<\/type>\n\t\t\t\t<scope>import<\/scope>\n\t\t\t<\/dependency>\n\t\t<\/dependencies>\n\t<\/dependencyManagement>\n\n\t<build>\n\t\t<plugins>\n\t\t\t<plugin>\n\t\t\t\t<groupId>org.springframework.boot<\/groupId>\n\t\t\t\t<artifactId>spring-boot-maven-plugin<\/artifactId>\n\t\t\t\t<configuration>\n\t\t\t\t\t<excludes>\n\t\t\t\t\t\t<exclude>\n\t\t\t\t\t\t\t<groupId>org.projectlombok<\/groupId>\n\t\t\t\t\t\t\t<artifactId>lombok<\/artifactId>\n\t\t\t\t\t\t<\/exclude>\n\t\t\t\t\t<\/excludes>\n\t\t\t\t<\/configuration>\n\t\t\t<\/plugin>\n\t\t<\/plugins>\n\t<\/build>\n\n<\/project>\n\n<\/code><\/pre>\n\n\n\n
You can see we’re adding the spring cloud streaming libraries as well as the mongodb ones.<\/p>\n\n\n\n
Now make the MessageEvent<\/code> class in com.bullyrooks.messagerepository.event.dto<\/code><\/p>\n\n\n\n
package com.bullyrooks.messagerepository.event.dto;\n\nimport lombok.AllArgsConstructor;\nimport lombok.Builder;\nimport lombok.Data;\nimport lombok.NoArgsConstructor;\n\n@Data\n@Builder\n@AllArgsConstructor\n@NoArgsConstructor\npublic class MessageEvent {\n    private String messageId;\n    private String firstName;\n    private String lastName;\n    private String message;\n}<\/code><\/pre>\n\n\n\n
This is the object structure that our event will serialize into<\/p>\n\n\n\n
Now copy over the MessageRepository<\/code>, MessageDocument <\/code>and MessageDocumentMapper <\/code>from the previous implementation (you can find them in the github history of the cloud-application<\/code> project if you didn’t stash the changes anywhere).  I put them into com.bullyrooks.messagerepository.repository<\/code> under document <\/code>and mapper <\/code>packages as needed.<\/p>\n\n\n\n
There is one change to callout though.  Since I don’t need a model object (the MessageDocument <\/code>will work) the mapper maps from the event to the document.<\/p>\n\n\n\n
@Mapper\npublic interface MessageDocumentMapper {\n    MessageDocumentMapper INSTANCE = Mappers.getMapper(MessageDocumentMapper.class);\n\n    MessageDocument eventToDocument(MessageEvent msgEvent);\n\n    MessageEvent documentToEvent(MessageDocument returnDoc);\n}<\/code><\/pre>\n\n\n\n
The MessageService <\/code>in com.bullyrooks.messagerepository.service<\/code> is very stripped down<\/p>\n\n\n\n
package com.bullyrooks.messagerepository.service;\n\nimport com.bullyrooks.messagerepository.config.LoggingEnabled;\nimport com.bullyrooks.messagerepository.event.dto.MessageEvent;\nimport com.bullyrooks.messagerepository.repository.MessageRepository;\nimport com.bullyrooks.messagerepository.repository.document.MessageDocument;\nimport com.bullyrooks.messagerepository.repository.mapper.MessageDocumentMapper;\nimport com.bullyrooks.messagerepository.service.model.Message;\nimport io.micrometer.core.instrument.Counter;\nimport io.micrometer.core.instrument.MeterRegistry;\nimport lombok.extern.slf4j.Slf4j;\nimport org.springframework.beans.factory.annotation.Autowired;\nimport org.springframework.stereotype.Service;\n\n@Service\n@Slf4j\n@LoggingEnabled\npublic class MessageStorageService {\n\n    MessageRepository messageRepository;\n    MeterRegistry logzioMeterRegistry;\n\n    Counter messageSaved;\n\n    @Autowired\n    public MessageStorageService(MessageRepository messageRepository,\n                                 MeterRegistry logzioMeterRegistry){\n        this.messageRepository = messageRepository;\n        this.logzioMeterRegistry = logzioMeterRegistry;\n        initCounters();\n    }\n\n    private void initCounters() {\n        messageSaved = Counter.builder(\"message.stored.count\")\n                .description(\"Number of messages successfully stored in the repository\")\n                .register(logzioMeterRegistry);\n    }\n\n\n    public MessageDocument saveMessage(MessageDocument msgDoc){\n        log.info(\"saving document: {}\", msgDoc);\n        MessageDocument returnDoc = messageRepository.save(msgDoc);\n        messageSaved.increment();\n        return returnDoc;\n    }\n}<\/code><\/pre>\n\n\n\n
Its essentially a copy of the one from cloud-application<\/code>, but it only writes to the repository.<\/p>\n\n\n\n
Now lets implement the spring cloud stream consumer.  Create a class called MessageEventConsumer <\/code>in com.bullyrooks.messagerepository.event<\/code> with this content<\/p>\n\n\n\n
package com.bullyrooks.messagerepository.event;\n\nimport com.bullyrooks.messagerepository.event.dto.MessageEvent;\nimport com.bullyrooks.messagerepository.repository.mapper.MessageDocumentMapper;\nimport com.bullyrooks.messagerepository.service.MessageStorageService;\nimport lombok.extern.slf4j.Slf4j;\nimport org.springframework.beans.factory.annotation.Autowired;\nimport org.springframework.context.annotation.Bean;\nimport org.springframework.stereotype.Component;\n\nimport java.util.function.Consumer;\n\n@Component\n@Slf4j\npublic class MessageEventConsumer {\n\n    @Autowired\n    MessageStorageService storageService;\n\n    @Bean\n    public Consumer<MessageEvent> consumeMessageEvent(){\n        return (eventIn) -> storageService\n                .saveMessage(MessageDocumentMapper.INSTANCE.eventToDocument(eventIn));\n    }\n}\n<\/code><\/pre>\n\n\n\n
This is all you need.  A component that injects the service.  The Bean defines the function which has a special signature.  The Consumer tells the function that it should expect a MessageEvent <\/code>object, this is different than a normal signature where the input is in the parenthesis.  Then we’re saying for each MessageEvent<\/code> (eventIn<\/code>), call the mapper and send the result to the storage service.  That’s all we have to do! <\/p>\n\n\n\n
the application.yaml<\/code> should look familiar we’ve seen the mongo, health and kafka configuration before<\/p>\n\n\n\n
spring:\n  application:\n    name: message-repository\n  cloud:\n    stream:\n      bindings:\n        consumeMessageEvent-in-0:\n          destination: message.created\n  kafka:\n    properties:\n      sasl.mechanism: PLAIN\n      bootstrap.servers: pkc-2396y.us-east-1.aws.confluent.cloud:9092\n      security.protocol: SASL_SSL\n  data:\n    mongodb:\n      uri: mongodb+srv:\/\/bullyrooks:${mongodb.password}@bullyrooks.4zqpz.mongodb.net\/bullyrooks?retryWrites=true&w=majority\nmanagement:\n  endpoints:\n    web:\n      exposure:\n        include: \"*\"\n  endpoint:\n    health:\n      probes:\n        enabled: true\n      show-details: always\n      group:\n        readiness:\n          include: \"readinessState,mongo,messageGenerator\"\n    metrics:\n      enabled: true\n\nlogging:\n  level:\n    root: INFO\n    com.bullyrooks: DEBUG\n    io.micrometer.logzio: WARN\nlogzio:\n  metrics:\n    url: https:\/\/listener.logz.io:8053\n    registry:\n      mock: false <\/code><\/pre>\n\n\n\n
The unique part here is that we’re defining an in<\/code> binding for the topic and we need to use the same topic name (destination<\/code>) that the cloud-application<\/code> is publishing to.<\/p>\n\n\n\n
The MessageEventConsumerTest <\/code>in src\/test\/java\/com\/bullyrooks\/messagerepository\/event<\/code> is going to look a little new though<\/p>\n\n\n\n
package com.bullyrooks.messagerepository.event;\n\nimport com.bullyrooks.messagerepository.event.dto.MessageEvent;\nimport com.bullyrooks.messagerepository.repository.MessageRepository;\nimport com.bullyrooks.messagerepository.repository.document.MessageDocument;\nimport com.github.javafaker.Faker;\nimport com.github.javafaker.service.FakeValuesService;\nimport com.github.javafaker.service.RandomService;\nimport lombok.extern.slf4j.Slf4j;\nimport org.junit.jupiter.api.Test;\nimport org.junit.jupiter.api.extension.ExtendWith;\nimport org.springframework.beans.factory.annotation.Autowired;\nimport org.springframework.boot.test.autoconfigure.data.mongo.AutoConfigureDataMongo;\nimport org.springframework.boot.test.context.SpringBootTest;\nimport org.springframework.cloud.stream.binder.test.InputDestination;\nimport org.springframework.cloud.stream.binder.test.TestChannelBinderConfiguration;\nimport org.springframework.context.annotation.Import;\nimport org.springframework.data.domain.Example;\nimport org.springframework.messaging.Message;\nimport org.springframework.messaging.support.GenericMessage;\nimport org.springframework.test.context.ActiveProfiles;\nimport org.springframework.test.context.junit.jupiter.SpringExtension;\n\nimport java.util.Locale;\n\nimport static org.junit.jupiter.api.Assertions.assertEquals;\n\n@ExtendWith(SpringExtension.class)\n@SpringBootTest\n@AutoConfigureDataMongo\n@Slf4j\n@ActiveProfiles(\"test\")\n@Import(TestChannelBinderConfiguration.class)\npublic class MessageEventConsumerTest {\n\n    @Autowired\n    MessageRepository messageRepository;\n\n\n    FakeValuesService fakesvc = new FakeValuesService(\n            new Locale(\"en-US\"), new RandomService());\n    Faker faker = new Faker();\n\n    @Autowired\n    private InputDestination inputDestination;\n\n    @Test\n    void testMessageStore() {\n\n        \/\/given\n        MessageEvent msgEventIn = MessageEvent.builder()\n                .firstName(faker.name().firstName())\n                .lastName(faker.name().lastName())\n                .message(faker.gameOfThrones().quote()).build();\n        Message<MessageEvent> messageIn = new GenericMessage<>(msgEventIn);\n\n        \/\/when\n        inputDestination.send(messageIn);\n\n        \/\/then\n        Example<MessageDocument> example = Example.of(\n                MessageDocument.builder()\n                        .firstName(msgEventIn.getFirstName())\n                        .lastName(msgEventIn.getLastName())\n                        .message(msgEventIn.getMessage())\n                        .build());\n        MessageDocument doc = messageRepository.findOne(example).get();\n        assertEquals(msgEventIn.getFirstName(), doc.getFirstName());\n        assertEquals(msgEventIn.getLastName(), doc.getLastName());\n        assertEquals(msgEventIn.getMessage(), doc.getMessage());\n    }\n\n}<\/code><\/pre>\n\n\n\n
We’re using the TestChannelBinderConfiguration<\/code> to inject an InputDestination <\/code>this time.  The input is a MessageEvent<\/code> that we wrap into a GenericMessage <\/code>object that we then post to that destination.  Additionally, since we don’t have an id to search the repo for, we use an example query object to search for the record we expect to be there.<\/p>\n\n\n\n
The default test for MessageRepositoryApplication needs an update as well.  It needs to know about mongo in order to actually be able to run.  Add these annotations<\/p>\n\n\n\n
@SpringBootTest\n@AutoConfigureDataMongo\n@ActiveProfiles(\"test\")\nclass MessageRepositoryApplicationTests {\n\n\t@Test\n\tvoid contextLoads() {\n\t}\n\n}\n<\/code><\/pre>\n\n\n\n
The application-test.yaml<\/code> in the src\/test\/resources<\/code> directory needs to know the mongodb version<\/p>\n\n\n\n
spring:\n  mongodb:\n    embedded:\n      version: 2.6.10 # Version of Mongo to use.<\/code><\/pre>\n\n\n\n
Finally, add the same environment configuration to the helm deployment.yaml<\/code> file as we did for cloud-application<\/code>, make sure to get the mongo config copied over as well.<\/p>\n\n\n\n
          - name: SPRING_DATA_MONGODB_URI\n            valueFrom:\n              secretKeyRef:\n                name: mongo-secrets\n                key: SPRING_DATA_MONGODB_URI\n          - name: SPRING_KAFKA_PROPERTIES_SASL_JAAS_CONFIG\n            valueFrom:\n              secretKeyRef:\n                name: confluent-secrets\n                key: SPRING_KAFKA_PROPERTIES_SASL_JAAS_CONFIG<\/code><\/pre>\n\n\n\n
Verifying<\/h2>\n\n\n\n
We could run this locally, but we won’t be able to test it directly unless we have a way to push messages onto the kafka topic.  One way to test is to run both cloud-application and message-repository locally.  You should see message requests generate events that are consumed by message-repository in the logs<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
2022-02-27 15:33:23,588 DEBUG [,] c.b.m.c.LoggingAspect: -> MessageStorageService.saveMessage invocation.  params: {\"msgDoc\":{\"messageId\":null,\"firstName\":\"Bully\",\"lastName\":\"Rooks\",\"message\":\"local test 123\"}}\n2022-02-27 15:33:23,592 INFO  [,] c.b.m.s.MessageStorageService: saving document: MessageDocument(messageId=null, firstName=Bully, lastName=Rooks, message=local test 123)\n2022-02-27 15:33:23,728 DEBUG [,] c.b.m.c.LoggingAspect: <- MessageStorageService.saveMessage returns:{\"messageId\":\"621bfc3369057f23a56b7d2e\",\"firstName\":\"Bully\",\"lastName\":\"Rooks\",\"message\":\"local test 123\"}.  Execution time: 138ms\n<\/code><\/pre>\n\n\n\n
Go ahead and push up the changes to your feature branch and then merge to main when the build succeeds.<\/p>\n\n\n\n
Verifying in the Cloud<\/h2>\n\n\n\n
Turn off all of your local instances.  They’re currently in the same consumer group as the okteto versions and could be the recipient of the message to process.  Hit the cloud-application endpoint for the okteto instance in postman<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
We should see the message in confluent<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
You can see the logs in Kibana<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
And you can see the full trace in Jaeger<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
In particular, you can see that the calls through the controller respond faster because the longer call to mongodb is not on the original request path now.<\/p>\n\n\n\n
Note:  there is an issue with OTEL and kafka tracing<\/a>.  I did have to make a change to my dockerfile in order to get it working:<\/p>
<\/p><\/blockquote>\n\n\n\n
ENTRYPOINT [\"java\",\"-Dotel.instrumentation.common.experimental.suppress-messaging-receive-spans=true\", \"-jar\", \"app.jar\"]\n<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
\nNow that we’ve got messages being published to kafka, we are going…\n<\/div>\n
Continue reading “Kube Cloud Pt5 | Create an Event Consumer”<\/span>…<\/a><\/div>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[41],"tags":[90,190,80,195,166,43,194,65],"course":[188],"class_list":["post-1356","post","type-post","status-publish","format-standard","hentry","category-software-development","tag-event-driven-architecture","tag-kafka","tag-kubernetes","tag-microservices","tag-observability","tag-spring-boot","tag-spring-cloud-stream","tag-tracing","course-kube-cloud-pt5-kafka-events","entry"],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":1339,"url":"https:\/\/bullyrooks.com\/index.php\/2022\/02\/27\/kube-cloud-pt5-create-an-event-publisher\/","url_meta":{"origin":1356,"position":0},"title":"Kube Cloud Pt5 | Create an Event Publisher","author":"Bullyrook","date":"February 27, 2022","format":false,"excerpt":"We're going to be updating cloud-application to remove the mongodb repository logic and replace it with an event publisher. Create a new branch from main git checkout -b migrate Update the pom.xml first, remove the mongodb dependencies  org.springframework.boot<\/groupId> spring-boot-starter-data-mongodb<\/artifactId> <\/dependency> ...  org.testcontainers<\/groupId> mongodb<\/artifactId> 1.16.3<\/version> test<\/scope> <\/dependency> and add\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-39.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-39.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image-39.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":1069,"url":"https:\/\/bullyrooks.com\/index.php\/2021\/07\/23\/spring-boot-lambda-implementation\/","url_meta":{"origin":1356,"position":1},"title":"Spring Boot Lambda Implementation","author":"Bullyrook","date":"July 23, 2021","format":false,"excerpt":"Now we're going to add some code. I'm going to follow my ports and adapters method of building a DTO and value object that I've used previously. Yes, its a bit of overkill for this project (especially a hello world example), but if you're using this course as a springboard\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2021\/07\/image-4.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2021\/07\/image-4.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2021\/07\/image-4.png?resize=700%2C400&ssl=1 2x"},"classes":[]},{"id":1258,"url":"https:\/\/bullyrooks.com\/index.php\/2022\/02\/13\/kube-cloud-pt3-rest-interaction\/","url_meta":{"origin":1356,"position":2},"title":"Kube Cloud Pt3 | REST Interaction","author":"Bullyrook","date":"February 13, 2022","format":false,"excerpt":"Now that we've got a new service, we're going to make it discoverable via kubernetes and call it from the cloud application service. Enable Kubernetes Features Let's start a new branch in our cloud_application project $ git checkout -b kube Switched to a new branch 'kube' Edit the pom.xml and\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/02\/image.png?resize=1050%2C600&ssl=1 3x"},"classes":[]},{"id":1242,"url":"https:\/\/bullyrooks.com\/index.php\/2022\/02\/13\/kube-cloud-pt3-synchronous-service-interaction\/","url_meta":{"origin":1356,"position":3},"title":"Kube Cloud Pt3 | Synchronous Service Interaction","author":"Bullyrook","date":"February 13, 2022","format":false,"excerpt":"In this course I'm going to show you how to make another spring boot microservice (message-generator), deploy it with our first service (cloud-application). I'll show how cloud-application service can discover message-generator via kubernetes services, call an endpoint in message-generator with a feign based REST client as well as how to\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/01\/image-45.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/01\/image-45.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/01\/image-45.png?resize=700%2C400&ssl=1 2x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/01\/image-45.png?resize=1050%2C600&ssl=1 3x, https:\/\/i0.wp.com\/bullyrooks.com\/wp-content\/uploads\/2022\/01\/image-45.png?resize=1400%2C800&ssl=1 4x"},"classes":[]},{"id":827,"url":"https:\/\/bullyrooks.com\/index.php\/2020\/03\/30\/simple-spring-boot-service-to-kubernetes-application-step-1-d67f80487848\/","url_meta":{"origin":1356,"position":4},"title":"Setup: IDE and New Project","author":"Bullyrook","date":"March 30, 2020","format":false,"excerpt":"\u00a0Its very easy to get a spring boot microservice up and running. You can read any variety of articles on medium (or other service) on how to do that. However, there\u2019s little about how to do some of the more complicated things that you need in order to support a\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":829,"url":"https:\/\/bullyrooks.com\/index.php\/2020\/03\/30\/simple-spring-boot-service-to-kubernetes-application-step-15-34e1bba8351b\/","url_meta":{"origin":1356,"position":5},"title":"Messaging and Event Driven Design","author":"Bullyrook","date":"March 30, 2020","format":false,"excerpt":"In order publish messages, we need a message broker and add some logic to use the message broker. We\u2019re going to use a cloud based SaaS service as a message broker and use spring cloud stream to interact with it. Setup the Message\u00a0Broker We\u2019ll need a message broker in order\u2026","rel":"","context":"In "Software Development"","block_context":{"text":"Software Development","link":"https:\/\/bullyrooks.com\/index.php\/category\/software-development\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/posts\/1356","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/comments?post=1356"}],"version-history":[{"count":8,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/posts\/1356\/revisions"}],"predecessor-version":[{"id":1372,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/posts\/1356\/revisions\/1372"}],"wp:attachment":[{"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/media?parent=1356"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/categories?post=1356"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/tags?post=1356"},{"taxonomy":"course","embeddable":true,"href":"https:\/\/bullyrooks.com\/index.php\/wp-json\/wp\/v2\/course?post=1356"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}