- Published on
Build Graphics Card Comparison Service - Development Log:3
- Authors
- Name
- Geonhyuk Im
- @GeonHyuk
I've implemented a Spring Boot app that sends HTTP GET requests to the Naver API server and retrieves product info, saving it to MongoDB collections. It's time to implement a user-subscription service that enables the user to subscribe to the products.
First, I initialized a Spring Boot project with the following dependencies, Spring Web, Spring WebFlux, Spring Starter Data JPA, and MySQL connector driver. Since the subscription service will send HTTP requests to the product service via WebClient, Spring WebFlux dependency needs to be included. And since the subscription service would use MySQL for databases, the project also includes JPA and MySQL connector dependencies.
Below is what the gradle.build file for subscription-service looks.
Below are the JPA entities.
There was a problem with query optimization. When marked only @OneToMany annotations to the list of subscription items in the Subscription entity, Hibernate automatically built an extra join table named "subscription_subscription_items", which impairs the performance of the queries. To fix this issue, I marked the subscription field in the SubscriptionItem entity with the @ManyToOne annotation. And I changed the fetch type to LAZY since the default fetch type EAGER loads all the associated data at once, making extra join tables, which leads to performance issues.
Source: Eager Fectching, @OneToMany Practices
To send an HTTP request to the running product service which runs on port 5000, I configured the webClient instance as below. .
Below are the service layer implementations.
\
Implementation of the Controller layer
The current API endpoint URLs for the subscription service are
GET http://localhost:5001/api/subscriptions/{id}
-> Retrieves all the subscribed items belonging to each subscription.
POST http://localhost:5001/api/subscriptions/{id}
-> Add an item to the subscription.
Those are not defined well, and I think I might change the endpoint structures later, perhaps while implementing security for my microservices.