• Java and .NET – Comparing Streams to LINQ

    In .NET, an easy way for you to simplify querying datasets is LINQ. Java doesn’t have this, but since the introduction of Java 8 in 2014, you do now have the possibility to use "streams". Both LINQ and streams are ways to simplify querying datasets and to provide developers with an easy API to use. Streams are similar to LINQ in many ways, but there are still some differences.

    February 23, 2017 by Raf Ceuls
  • How to Web App Manifest

    Like you surely noticed, there’s been a lot going on about Progressive Web Apps: How most people see them as the future of web apps in general, and how PWAs are trying to bridge the gap between web apps and native apps. In case you forgot what PWAs are, just check out Three Reasons Why Progressive Web Apps Are the Future.

    January 12, 2017 by Sara Barrera Riano
  • App Security in Microservices - Back to Basics at Devoxx 2016

    This year’s Devoxx was once again awesome. With all the commotion around microservices, I felt I had to go see Sam Newman’s talk “Security and Microservices” (amongst others). Newman is the author of Building Microservices (2015), a book aimed at developers to fully grasp the meaning of a microservice architectural design.

    December 7, 2016 by Maarten Vandeperre
  • Three Reasons Why Progressive Web Apps Are the Future

    As all die-hard front-end developers may already know, the yearly "Fronteers Conference" in Amsterdam (the Netherlands) is the place-to-be for all things front-end. This year's speakers focused on accessibility, responsive CSS, performance and Progressive Web Applications (PWAs). For those of you who have yet to be introduced to a "PWA", it’s basically the latest buzzword for how we should build web apps in the near future. One of the talks on PWAs was given by Nolan Lawson, web developer for Microsoft and open-source JavaScript contributor.

    November 18, 2016 by Jeroen Savat
  • Automatic mocking of spring beans with MockedLoader

    The problem

    We all love unit testing and Spring's JavaConfig. And we certainly dig them beans, however for unit testing we need to mock or instantiate our beans with Test @Configuration classes (or reuse existing @Configuration classes).

    In the case of mocking, we might see that adding an extra @Autowired dependency in e.g. a Service class, might break some tests...well .. sometimes a lot of tests.

    July 18, 2016 by Marc Vanbrabant