Do you want to know how to develop your skillset to become a Java Rockstar?
Subscribe to our newsletter to start Rocking right now!
To get you started we give you our best selling eBooks for FREE!
1. JPA Mini Book
2. JVM Troubleshooting Guide
3. JUnit Tutorial for Unit Testing
4. Java Annotations Tutorial
5. Java Interview Questions
and many more ....
Email address:

Running around the block: a dummy’s first encounter with AWS Lambda


It all started when the Egyptians slid a few marbles on a wooden frame to ease up on their brains in simple arithmetic; or perhaps when the Greeks invented the Antikythera Mechanism to track the movement of planets to two-degrees-per-millennium accuracy. Either way, computing has come a long way by now: Charles Babbage’s Analytical Engine, Alan Turing’s Enigma-breaker, NASA’s pocket ...

Read More »

Prefer System.lineSeparator() for Writing System-Dependent Line Separator Strings in Java

JDK 7 introduced a new method on the java.lang.System class called lineSeparator(). This method does not expect any arguments and returns a String that represents “the system-dependent line separator string.” The Javadoc documentation for this method also states that System.lineSeparator() “always returns the same value – the initial value of the system property line.separator.” It further explains, “On UNIX systems, ...

Read More »

How to Create Spring Boot Project With Spring initializer


Hello Friends, If you have used Spring framework previously, you must be aware that it takes some genuine effort to even get started with basic Spring functionality.With Spring Boot, that initial hassle is gone and you can get started in minutes. Welcome to the world of Spring Boot!!!           In this tutorial, we will see various ways in ...

Read More »

Solid Principles: Dependency inversion principle

Up until now we had a look on the single responsibility, open/closed, liskov substitution and interface segregation principles. Dependency Inversion is one of the last principle we are gone look at. The principle states that A. High-level modules should not depend on low-level modules. Both should depend on abstractions. B. Abstractions should not depend on details. Details should depend on ...

Read More »

Solid Principles: Interface segregation principle

Previously we examined the liskov substitution principle. Next principle is the interface-segregation. The interface-segregation principle (ISP) states that no client should be forced to depend on methods it does not use. Imagine an interface with many methods in our codebase and many of our classes implement this interface although only some of its methods are implemented. In our case the ...

Read More »

Docker Tutorial for Java Developers

Course Overview Docker is a computer program that performs operating-system-level virtualization also known as containerization. It is developed by Docker, Inc. Docker is primarily developed for Linux, where it uses the resource isolation features of the Linux kernel such as cgroups and kernel namespaces, and a union-capable file system such as OverlayFS and others to allow independent “containers” to run ...

Read More »

Solid Principles: Liskov substitution principle

Previously we took a dive into solid principles including the single responsibility and the open/closed principle. The Liskov substitution principle (LSP) is a particular definition of a subtyping relation, called (strong) behavioral subtyping, Supposing object S is a subtype of object T, then objects of type T may be replaced with objects of type S without altering any of the ...

Read More »

Docker for Java Developers: Continuous Integration on Docker

This article is part of our Academy Course titled Docker Tutorial for Java Developers. In this course, we provide a series of tutorials so that you can develop your own Docker based applications. We cover a wide range of topics, from Docker over command line, to development, testing, deployment and continuous integration. With our straightforward tutorials, you will be able ...

Read More »

Solid Principles: Open/closed principle

Previously we talked about the single responsibility principle. The open/closed principle is the second principle in the row regarding the solid principles acronym. “Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification” By employing that principle the goal is to extend a module’s behaviour without modifying its source code. Imagine a scenario of applying ...

Read More »