The Most Popular Microservice (Is Written In Java)

One of the most popular microservice is Jenkins CI:

  1. Jenkins was initially created by a very small team (Kohsuke Kawaguchi)
  2. Jenkins plays well with other services like GitHub, SVN, Git using HTTP and REST-like APIs. In fact Jenkins is very popular in non-Java environments.
  3. The state is managed by each Jenkins instance individually in an own repository (JENKINS_HOME)
  4. Services are exposed via Remote API
  5. The UI is self-contained
  6. Jenkins can be easily extended by an independent team
  7. Jenkins is already packaged as a micro service: just launch the service with java -jar jenkins.war

However, I bet Kohsuke didn't knew the term "microservice" as he initially developed Hudson :-).

See you at Java EE Workshops at Munich Airport, Terminal 2 or on demand and in a location very near you:


So whats next, are you going to call SAP a microservice?

Posted by Chooty on September 25, 2014 at 06:14 AM CEST #


nowadays you can call any reasonably designed application a "microservice". A few years ago you could do the same with "SOA".



Posted by Adam Bien on September 26, 2014 at 06:00 AM CEST #

Java EE 7 Bootstrap, Monday, December 8th, 2014
Effective Java EE 7, Tuesday, December 9th, 2014
Java EE 7 Architectures, Wednesday, December 10th, 2014

I'm considering going to each of these workshops. Are there a lot of similar material in each workshop or are there different topics? Are the workshops structured so you get a benefit from going to several of them? :)

Posted by Jorgen on September 26, 2014 at 10:57 AM CEST #

Hi Jorgen,

thanks for your interests!

1. With Bootstrap I'm going to introduce the attendees into the JavaEE ideas and implement "Hello World" to explain the basics.

2. In Effective I will implement an application based on "Best Practices" and delve more into details.

3. In the Architectures talk I will explain higher level concepts, modularization, versioning etc.

See also: and

See you soon! :-)



Posted by Adam Bien on September 30, 2014 at 03:48 PM CEST #

Hi Adam,

Jenkins contributor here, happy to see your enthusiastic interest for Jenkins, but surprised you consider it to have a "microservice" architecture. Jenkins is a plugin-based platform, which shares some benefits with microservices (component maintained by independent teams) but nothing more, and the other points you notice are unrelated to microservice architecture. _Some_ service are actually exposed via remote API but this is not the primary way to link them together. Also how using JENKINS_HOME to store xml files relates to micro-services ? Wonder you were drunk writing this :P

Posted by Nicolas De Loof on October 01, 2014 at 05:44 AM CEST #


internally Jenkins plugins are not exactly a MSA, although sometimes OSGi also claims that it is a micro services architecture.

However: I would consider Jenkins from the outside perspective as a micro service: it is self contained, accessible via simple protocols and used for orchestrations or as a orchestrator.

More on that:

thanks for contributing to Jenkins and commenting!,



Posted by Adam Bien on October 04, 2014 at 08:45 AM CEST #

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