#oj9 — Public Fediverse posts

#Enterprise #Message #Queues require a different mindset than batchwise #processing. With an #EMQ one gets nudged to handle 1 message at a time. It needs #software #languages that have quick start-up times. Historically, #Java has a bad rep for that.

With #Java11 and IBM
's #OJ9 the cold-start speed of a program can be greatly increased (vs Oracle
's #Hotspot) to the point where the program no longer needs to run forever... which is why we can use it on #AwsLambda with #Kafka.

#Enterprise #Message #Queues require a different mindset than batchwise #processing. With an #EMQ one gets nudged to handle 1 message at a time. It needs #software #languages that have quick start-up times. Historically, #Java has a bad rep for that.

With #Java11 and IBM
's #OJ9 the cold-start speed of a program can be greatly increased (vs Oracle
's #Hotspot) to the point where the program no longer needs to run forever... which is why we can use it on #AwsLambda with #Kafka.

I'm increasingly impressed by the speed of my #Java #software applications. Running on the #OJ9 VM based on #OpenJDK11, with caching of shared classes activated, an order audit between our local #ERP and a remote #RESTAPI can take less than 5 seconds from cold start to finish.

Now these are batch processes so usually I don't care too much about their run duration. But still: noticably faster than Java 1.8.