Ashish Choudhary

"The primary reason for this poor response time could be due to the network. Our Redline13 load testing tool was set up in the AWS W. Virginia region, whereas the Spring Boot pet clinic application was deployed in AWS US-west1 (N. California) region. Since transactions had to be made across the country, response time could have been degraded". This latency between AWS regions should be in ms not seconds or I am missing something.

Thanks for your inputs. From the documentation it seems it can be used. I will verify this and update the article.

Thanks for your inputs. Not an issue. Maybe I should have added few lines about it. I wanted to cover it, but I also wanted to give an overview of the record class with some practical scenarios. And I do try not to go above certain word limits with my articles. Now coming back to your point, are you talking about how the record class serialization works with Spring Boot? To answer that, I think the Jackson dependency added support for records, and it handles the serialization and deserialization part. Let me see if I can update the article or write a new one to cover the serialization and deserialization of records.

I am glad you liked it. You can use them as DTO. As per the following JPA specifications, records cannot be used as JPA or Hibernate entities.

1. The entity class must have a no-arg constructor. You cannot create a no-arg constructor with Records.

2. The entity class must not be final. Records are final.

3. No methods or persistent instance variables of the entity class may be final. Fields are final in the records class.