Victor Tsoukanov

Which is faster Assembler or C++? Sure, C++ would be a loser in every way. Your question is not correct. You are selecting particular language for development at first and if you need to have performance you need to have scalable design which does not depend on language at all.

I think main thing that should be clarified is "how happy will you feel yourself on the new job". With provided questions you will not be able to find it out. I think in the middle of you list you will get very angry person right near you. People do not like to be judged. I think the most important thing that should be clarified is what they are waiting from you and try to compare it with your expectations to avoid disappointment in the future.

One additional hint - use class filtering in profiler and start it with your own packages. While without filtering there may be a lot of information in snapshot difference, after applying filter you can reduce it to small set of your classes which may be a cause of memory leak.

If you do not want to pay money for profiling tool, there is a free and quite suitable profiler – Netbeans profiler

• a database is not performant
• a database is not a performance bottleneck if you are using in-memory database
• a (replicated) cache brings as much drawbacks as session. And you need to produce some extra code/configuration
• memcached is a simple cache with easy configuration

• a database is not performant
• a database is not a performance bottleneck if you are using in-memory database
• a (replicated) cache brings as much drawbacks as session. And you need to produce some extra code/configuration
• memcached is a simple cache with easy configuration

Don't Use the Session - it is very categorically. If you need scalability you can develop your own session replication if container does not provide it. For example you can use HttpSessionListener and HttpSessionBindingListener to trace changing of session attributes and save values in distributed cache or database.

when you are using

Preconditions.checkArgument((i > 0), "The value i has to be greater than zero"); 

you create new string value that may not be used at all. Imaging how many such strings you can introduce and how long will GC collect them. And look at the following

if (i > 0) { throw new IllegalArgumentException ("The value i has to be greater than zero"); } 

agreed, some of them will be cached, may be in enterprise java it does not matter, but when you develop high-loaded application (e.g. in Telco domain) it matters

It is just a remark, Component.enable() had been deprecated and usage of Component.setEnabled(boolean) looks better

cancelButton.setEnabled(currentState.in(Order_State.PENDING, Order_State.PROCESSING, Order_State.CHECKING_CREDIT));

Hi, you are not right, I understand how maven works and what is it (a have a year experience with maven), but I still have strong conviction it was a wrong choice since it is too complex for such simple thing as dependency management.

Hi, I do not understand why it is not a dzone material - it is my opinion (as you see it was tagged as opinion). Also it was not a question - there were shown a simpler way for dependency management.