Concurrent Programming with Java EE 7 and Java SE 8--Free Article

Java EE 7 is exciting, but combining this lean platform with Java 8 brings even more power with less code. In this free JavaMagazine article "Concurrent Programming with Java EE 7 and Java SE 8 I implemented some examples (23 listings :-)) to discuss this "synergy". For more concurrency control and statistics take a look at

For even more Java EE 7 + Java 8 concurrency see you at Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting We will particularly focus on resiliency and concurrency during the Java EE Microservices workshop.

NEW: Online Workhop Effective WebApps without Frameworks is also coming to: MUC Airport.

Airport MUC workshops: Web (SPA, PWAs, Offline, Desktop, Mobile) Applications Essentials and Effective Web Applications. No migrations. #usetheplatform

Podcast: and newsletter:

A book about rethinking Java EE Patterns


Why use porcupine instead of JSR-236? I thought direct usage of thread pools, etc, was a bad practice because it could cause trouble for container lifecycle.

Posted by jieryn on February 06, 2015 at 02:00 PM CET #


Porcupine uses JSR-236 managed threads in fully "compliant" way.

Why to use it?

1. Statistics are available for the app.
2. You can configure the "overload" behavior per thread pool.
3. You can create multiple thread pools on-the-fly.
4. You have full control over the configuration.

But you are right--if you don't need the flexibility, JSR-236 is just fine. In fact I use mostly plain JSR-236 without porcupine in most projects,

thanks for your feedback!,


Posted by Adam Bien on February 06, 2015 at 02:04 PM CET #

The article cannot be read without subscription.

Posted by javaservant on February 08, 2015 at 02:12 PM CET #


Posted by xyz on February 09, 2015 at 07:13 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
Online Workshops
...the last 150 posts
...the last 10 comments