Java Performance Tuning

Java(TM) - see bottom of page

|home |services |training |newsletter |tuning tips |tool reports |articles |resources |about us |site map |contact us |
Tools: | GC log analysers| Multi-tenancy tools| Books| SizeOf| Thread analysers| Heap dump analysers|

Our valued sponsors who help make this site possible
JProfiler: Get rid of your performance problems and memory leaks! 

Training online: Concurrency, Threading, GC, Advanced Java and more ... 

News November 2014

Get rid of your performance problems and memory leaks!

Modern Garbage Collection Tuning
Shows tuning flow chart for GC tuning

Java Performance Training Courses
COURSES AVAILABLE NOW. We can provide training courses to handle all your Java performance needs

Java Performance Tuning, 2nd ed
The classic and most comprehensive book on tuning Java

Java Performance Tuning Newsletter
Your source of Java performance news. Subscribe now!
Enter email:

Training online
Threading Essentials course

Get rid of your performance problems and memory leaks!

Back to newsletter 168 contents

The new buzzword is microservices. It means splitting your system up into multiple small processes with each process providing a smaller set of highly focused services. While the buzzword is new, the actual architecture is old, and a lot of you have been creating microservices for a long time now.

A note from this newsletter's sponsor : Deep dive Application Performance Monitoring
Fix performance issues with Java, .NET and Ruby platforms.
*** Monitor one app instance starting at $9 ***.

If your system is not just one big application server and it has multiple JVMs, then almost certainly you already have a microservice architecture in place. At the very least, as Adam Bien pointed out it's likely that you are already running one of the most popular microservices around - Jenkins CI!

The advantage of a microservice architecture is that you only need to scale the services that need scaling, rather than all components; this reduces complexity (you don't have to worry about scaling issues for those components that are not scaled), reduces resource usage (fewer things are scaled), and increases the ease of scaling (you are scaling fewer components, that'll be easier all round); scaling horizontally is easier (it's easier to cluster enable a component than a whole service, e.g. no need to scale up database connections if the microservice doesn't need those) and you prefer to scale horizontally if possible as that lets you scale cheaply. The disadvantage is that you need to be much more rigorous in decoupling your components and there is additional deployment and distributed monitoring complexity.

One of the talks I reference this month is an excellent one on testing microservices - so let's get right on to that and all our usual sections: links to tools, articles, news, talks and as ever, all the extracted tips from all of this month's referenced articles.

A note from this newsletter's sponsor

New Relic - Try New Relic today and get your free Data Nerd shirt!
Free SaaS APM tool to monitor, troubleshoot, and tune apps
running on Websphere, Weblogic, Tomcat, Jetty, JBoss, Solr, Resin


Java performance tuning related news.


Java performance tuning related tools.

A note from this newsletter's sponsor

Get total visibility in just 15 minutes with AppDynamics PRO,
A performance monitoring tool for Java/.NET apps.
It installs in minutes. Start your FREE TRIAL today.


Jack Shirazi

Back to newsletter 168 contents

Last Updated: 2024-01-29
Copyright © 2000-2024 All Rights Reserved.
All trademarks and registered trademarks appearing on are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries. is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
RSS Feed:
Trouble with this page? Please contact us