When you come from a Java background like I do and you take a look at JavaScript, the sheer mass of tools is overwhelming. The ecosystem is evolving very fast with new tools coming up every couple of months. Below, I tried to give a comparison between Java build tools and their equivalent in the JavaScript world.

Whenever you write an AngularJS application, you will use modules. Modules divide your application into small logical units. Some units might depend on others, while some might be totally independent.

AngularJS provides three different ways to create a service:

Program to an interface, not an implementation.

Whenever you build software, you want to create reusable and independent components. In the world of user interfaces, those components are often called widgets. Here’s an example how we can achieve this with AngularJS.

Every backend application has a boot process. Services must be instantiated, connections must be established and configurations must be loaded before the application is ready. How can we achieve something similar for an AngularJS application?

Last week I attended an AngularJS Intensive Workshop by Robin Böhm from Symetics GmbH. Symetics is the company behind www.angularjs.de and provides consulting and training all around JavaScript, AngularJS (1/2) and TypeScript.

I’m a Windows user. I don’t use OSX, I don’t use Linux, I use Windows. For real. Usually I develop Java or JavaScript applications which perfectly run under Windows, Linux, OSX or whatsoever. So developing under Windows is no problem at all. Runtime environments, IDEs, editors - Windows has it all. However, people keep wondering how I can do the most simple task:

Many web apps have a very simple security concept based on user roles. You might have some admin, some common users and maybe some more roles like a moderator or a super-user. Such a role concept can be easily implemented with Spring Security. For example, you could secure your app based on routes which are available for certain roles:

One of the biggest strengths of Spring is its ability to make your code testable. By using dependency injection and inversion of control, the Spring context defines which objects will be wired into your beans. This makes it easy to wire services, repositories or what ever you like. But how to wire mocks in your tests?