Microservices in Java – A Second Look

Re:Microservices in Java – A Second Look by empthought on Wednesday October 18, 2017 @03:40PM (#15502247)

This line of argument to favor Go over Python or Java is just as valid as the line of argument to favor C over Go. Benchmark OpenBSD http + FastCGI C vs. this.

[ Parent | on HN ]

Re:Microservices in Java – A Second Look by paulddraper on Wednesday October 18, 2017 @03:42PM (#15502262)

THe better argument would be sane concurrency, which Go does better than nearly every other language.

[ Parent | on HN ]

Re:Microservices in Java – A Second Look by merb on Wednesday October 18, 2017 @03:47PM (#15502302)

*without a library

comparing any go concurrency with any java/whatever language concurrency still might lack behind.

just java has so many concurrency libraries that are better than the built-in go concurrency mechanism.

even java8 made things way better.

[ Parent | on HN ]

Re:Microservices in Java – A Second Look by bsaul on Wednesday October 18, 2017 @03:55PM (#15502377)

I've recently regained interest in java, so i'm interested if could you give a brief explanation on the "better than built in go concurrency" ?

[ Parent | on HN ]

Re:Microservices in Java – A Second Look by maltalex on Wednesday October 18, 2017 @05:53PM (#15503553)

I suggest you take a look at RxJava and Akka.

RxJava is a reactive programming library from Netflix. Akka is a framework for writing applications using the actor model.

[ Parent | on HN ]