Serguei Cambour

Thank you for sharing! One point which is rather about code convention, - you don't need to prefix with `this` when calling finder methods on a repository instance in the controller:

```

this.repository.findAll(...)

```

It's getting too noisy to read the code and the compiler will do it for you. Usually, you should use it only when assigning a new value.

I'd say that the term itself "Microservice framework" is totally wrong. You can provide an API using this or another language (Java, Go etc.). Why not mention Ruby or Elixir for example, - both can be used in mode API at ease.

Thank you for sharing. Two points though:

1. I don't see the need to call `super` in the abstract class `Customer`.

2. You should use either a threshold value to get more accuracy or even better use BigDecimal with compareTo() method to compare 2 double values, never use just '=='.

I think you don't need to annotate name attribute with

@JsonProperty("name")

as it will be the same by default, - use it only if the JSON attribute name is different from Java one.

So true and applied to the current team and project I joined since 4 months.

Thank you very much for sharing, really useful!

Thank you for sharing, Sebastian ! It would be great to indicate the type of git variable in the the following expresion:

Git.cloneRepository()

 .setDirectory(workingDir)

 .setTransportConfigCallback(transportConfigCallback)

 .setURI("ssh://example.com/repo.git")

 .call();

Regards

Thank you for sharing ! Sure, Java has still a long way to go to get more readability compared to Ruby for example.

If we consider that calling a method is as if we are sending a message, in this case used methods names (accept, visit) are so cumberscome and just bring the ambiguity.

yep, correct :)

Ar least the last 3 versions have it.

It is a little bit outdated to create a Maven-aware project like that (create a testrest folder, then src/main/java folder, etc.). As in the very beginning you were using Eclipse IDE, why not just ask Eclipse to create an empty Maven project ? In this case you don't need to run mvn eclipse:eclipse any more.

It seems like some dependencies are missing (slf4j):

mvn exec:java -Dexec.mainClass="com.controller.HelloRest"

I got the below error:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.