Remove Guava from dependency and use JDK 8 classes instead about scalecube-services HOT 4 CLOSED

@antonkharenko i was starting to work on removing guava as dependency and during my work i found that maybe its not so good idea to remove guava just yet. the value of removing guava is very small comparing to the features it brings and from code clarity point of view

there are some obvious things that we might not want to use guava
but there is also stuff that will just create code duplication of guava.

i suggest to only reduce the dependency on guava for example when i comes to requireNonNull but apart of that i dont see much value.

so i suggest to close this ticket and maybe open new one with more specific code changes rather than removing guava totally.

from scalecube-services.

There is no specific need for this ticket as for now. Idea was that we use guava classes in very trivial cases only. But if not it can be kept. Or it can be removed and left where more advanced use cases is needed - like remove from Transport and Cluster and leave in Service or so.

from scalecube-services.

services almost not using it mostly cluster and transport use it
the use of services is argument check. that is 3 lines of code.

the more problamatic zones are the InmmutableMaps MultiMaps and thread factory usage in cluster and in transport.

check my pull request and changes it gives some insights

from scalecube-services.

ok, I will review them

from scalecube-services.