Spring DATA Mongo. Testing your mongo using in-memory db

######Embeddable When I was a bit younger, I couldn’t understand why more senior engineers stood for embedding builds as much as it’s possible. For instance, you have a database, and you’re running your integration tests only with in memory databases. It was very unusual for me, why having a working database on your local machine, you’re using some weird in memory things ? The time have passed, and I understand now, that embedding your builds is a good practice, because: It reduce your build time It decouples your build phase from any environments Even if you don’t have any database/thirdparty tool installed on your local machine, your build will finish successfully, and after then you can start installing all required third party instruments. Fongo + NoSQl-Unit By this article I’d like to show how to effectively test your Spring DATA repositories using Fongo - an in-memory implementation. I’m not going to explain how Spring Data works, you can read their documentation here Say, you have following repository package org.example.repository; import org.springframework.data.mongodb.repository.MongoRepository; import org.springframework.data.mongodb.repository.Query; import org.startup.queue.domain.Establishment; import java.util.Optional; public interface SomethingRepository extends MongoRepository<Establishment, String> { Optional<Something> findByCol1(String col1); } Next, test it: package org.example.repository; import com.github.fakemongo.Fongo; import com.lordofthejars.nosqlunit.annotation.UsingDataSet; import com.lordofthejars.nosqlunit.core.LoadStrategyEnum; import...

Spectacleapp - forget about your mouse. OSX only.

If you’re interested in reducing interaction with your mouse - then use this program. Link - https://www.spectacleapp.com/ If you want easily locate your terminals - then it’s a good instrument for you PS - it’s especially useful to move app between your physical monitors. And in case of many Desktops. I found this on their github https://github.com/eczarny/spectacle/issues/15

Dockerizing your apps

Preface As some of you may already know, from the last autumn-2015 I’m working as a software engineer in startup company called Upwork, in one of teams. From the time I started working there, I realized, that working on freelance basis is completely different from office work, even if you’re working on a good quality freelance job. Why ? At least, because you cant share some knowledge with your coworkers by cuf of coffee in your lunch time. So I decided to convert my blog to some R&D investigation. That’s why I’d like to warn you, that everything here is just an investigation, which I do on my free time, so don’t take it so critically, if you find something, which you don’t agree with, just comment, and let’s discuss. Technologies are changing every day, and we need to follow the trend, don’t we ? Why containers ? Before I can proceed with explanation in my head what is the definition of container, let’s return to the near part times, where we did everything manually: the dyno age, where it was ok to assemble your proeject war manually, and deploy it to the server in the same way. Then, the...

Lazybones - a cool instrument, which can save your time during a project setup

How long does it takes for you to create a new project ? And how often are you doing this routine job ? Do you remember, how interesting for you is to test some feature, which you want to test/try, but how hard is it to configure initial project ? There’s so many frameworks in java world, and for me it’s extremely hard to remember initial steps and configurations for each of them. And logically, if you do al this teps by your hands, then something can potencially go wrong Let’s start with a question “Why you need to create a new project”: You’d like to test something in your favorite project. You’re working in a microserviced worlds, and you start new microservice every day… You need to create a POC and test how it works. Anything else Personally I don’t want to store all this configuration steps in my head, and I prefer to use something, which can the work for me. That’s why I’d like to recommend a cool instrument for creating project skeletons in extremely convenient way - lazybones. Let’s demonstrate how to setup a Gatling project lazybones create https://bintray.com/ivanursul/lazybones-templates/download_file\?file_path\=gatling-template-0.1.zip load-tests Quite easy, don’t you find ?...

How to work with maven javacc plugin

I had to do some work with google-visualization-java github project. I needed to change some logic for correct google visualization query. I found, that guys were using javacc compiler. Official site says: Java Compiler Compiler tm (JavaCC tm) is the most popular parser generator for use with Java tm applications. A parser generator is a tool that reads a grammar specification and converts it to a Java program that can recognize matches to the grammar. In addition to the parser generator itself, JavaCC provides other standard capabilities related to parser generation such as tree building (via a tool called JJTree included with JavaCC), actions, debugging, etc. To inject javacc inside your maven project, add following plugin <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>javacc-maven-plugin</artifactId> <version>2.5</version> <executions> <execution> <id>javacc</id> <goals> <goal>javacc</goal> </goals> <configuration> <sourceDirectory>${basedir}/src/main/java</sourceDirectory> </configuration> </execution> </executions> </plugin> Steps you need to do with your javacc project: Open terminal cd to project mvn clean generate-sources That’s it.