Tim Holloway wrote:connects, submits data, gets a single response returned as quickly as possible, then closes the connection until it makes the next request (if any). That's a basic characteristic of the Internet and not a Java or Spring - or cloud - limitation.
Spring Cloud Gateway is built on Spring Boot 2.x, Spring WebFlux, and Project Reactor. As a consequence, many of the familiar synchronous libraries (Spring Data and Spring Security, for example) and patterns you know may not apply when you use Spring Cloud Gateway
Problems may occur if you allow the client to set fields of type LocalDate, LocalTime and LocalDateTime. In general it's not a good idea to use the same class to both represent data in your database and data received from the client. For instance, what if I POST your JSON example from Germany? First of all, why can the client POST commentId, createdAt and updatedAt at all? Those fields should be determined by the server, not the client
Yes I will check this out and post the results here.
You can find out which of the two does it by printing the value of comment.updatedAt before you save it in the repository and after you retrieve it from the repository