Most of us use git as a version control tool and it isn't a surprise. It's very useful but it has one drawback - we can waste hours while solving problems. Also there is a very good reason why git related questions are at the very top on Stackoverflow - many people understand the idea of Git and version control but not many know how it works. That's why I'm going to unmask Git and show how it really works.
The daily struggle of managing, modifying and extending build configuration of complex software systems can lead to the necessity of writing complex command line scripts or managing huge configuration files.
Apart from constructing, the software engineering process must take into consideration the third party dependency injection and phases like testing, packaging and deployment.
Since Flux and Redux gained popularity, the approach to front-end architecture has changed drastically. The idea of a store with global application state, unidirectional data flow, immutability and changes using actions, largely increased the popularity of Redux-based frameworks.
Spring Boot is an framework, based on top of Spring Framework, to build Java applications as fast as snapping fingers. It provides things such as connectivity to databases, metrics, auto-configuration. You don't have to configure the low level code to get up and running, just use Spring Boot and get off the ground very quickly.
It's also very good in case of developing your application - stop wasting your time for boilerplate configuration - just add some dependencies and run the application. It is as simple as it sounds.
Querydsl is a Java open-source project that supports statically typed queries. It provides a typesafe querying layer on top of JPA, JDO, JDBC and other backends through the use of various modules. The framework uses an annotation processor to generate Java types based on JPA entities. In this short article I’ll be focusing on Querydsl’s queries support for JPA and how it can be used as an alternative to Criteria Api. Of course the framework also allows to modify and delete records by JPAQueryFactory methods.
Distributed systems have been around for a while. Since like 1970s we’ve been building applications with large scale in mind, and large availability. We went even more in that direction since the Internet Bubble around ‘95 and we still carry on. Then, at the beginning of 2010s, the microservices happened. “Fine grained SOA", how Adrian Cockcroft, former director for the Cloud Systems at Netflix described them, took over the development world.
In the previous article I presented the main idea of Mutation Testing. In order to better understand this concept, so far, my reflections covered only an example of a simple code where Traditional Mutation Operators have been used. In this part, you will get introduced to the concept of subsequent groups of Mutation Operators. I will show you also how to configure PIT with the Intellij IDEA.
All experienced developers have a good understanding of how significant for the quality of the product is a source code covered by high quality test suites. Depending on a company or even a team, we can come across many different test procedures and test frameworks. Regardless of that, at the end of the day, we are faced with a codebase covered by tests.