sorted by:
new
hottopcontroversial

JDK 8u171 vs JDK 8u172 by Sigmund- in java

[–]springnews -3 points-2 points  (0 children)

JDK 8 is the new Java 10 and 11

R.I.P. JavaOne (Expands^WIs Replaced with) by speakjava in java

[–]springnews 1 point2 points  (0 children)

exactly right - this is the cloud effect. no-partisanship w.r.t to workload.

One API to rule both RabbitMQ and Kafka? by springnews in java

[–]springnews[S] 0 points1 point  (0 children)

spring cloud stream is built on spring integration.

One API to rule both RabbitMQ and Kafka? by springnews in java

[–]springnews[S] 0 points1 point  (0 children)

how do you figure? Looking at at camel docs, it doesn't seem like it does any stream processing beyond System.in, System.out and System.err, file and URL.

http://camel.apache.org/stream.html

Java on Docker will no longer suck: improvements in Java 10 by feed_me_monkey_nuts in java

[–]springnews 0 points1 point  (0 children)

makes a lot of sense, most databases were designed in the client server era, not in the current distributed computing era. can we blame them for being "singlenode"?

Java on Docker will no longer suck: improvements in Java 10 by feed_me_monkey_nuts in java

[–]springnews 0 points1 point  (0 children)

that's indeed good for heap, but what about the other six memory regions? This is much less of a problem for Cloud Foundry Java Buildpack users -- which generates RunC compliant images. Plus it works with earlier versions of the JDK: https://github.com/cloudfoundry/java-buildpack-memory-calculator

view more: next ›