SivaLabs

It’s been tough time for everyone due to the Corona virus situation. Staying at home for weeks and weeks is not easy, but it is very necessary thing to do so that we don’t spread the virus.

However, if I look on the bright side I used to spend minimum 3 hours for office commute everyday. Now I am using that time for various other activities including learning some new things.

While building the software, we all agree, as a team, to follow a set of guidelines which are typically considered as best practices. But during the development, developers might violate those guidelines unknowingly or ignorance. Typically, we rely upon code reviews or code quality checking tools like SonarQube, PMD, etc. to check for such violations. But some of the guidelines could be opinionated decisions which might not be able to automate using SonarQube, PMD etc.

I come across many blog posts from various sources like Twitter, StackOverflow, etc., and some of them are very helpful. Also, in day-to-day work I learn a few new things, explore some new tools. Usually I keep track of this information using Browser Bookmarks and Pocket.

I thought maybe this information could be useful for others too. So, I am going to share it weekly on my blog.

One of the many reasons for the huge popularity of Spring and SpringBoot is its great support for Testing. We can write unit tests using Mockito without requiring any Spring features. And, we can write Integration Tests using Spring testing support by creating Spring ApplicationContext.

I have been working with Spring and Spring Boot for many years, and I needed to create a lot of Spring (Boot) applications for various reasons, like blog posts, sample apps, book sample code, and for my personal learning as well. So, I needed some tool/mechanism to quickly create a Spring (Boot) application with the most commonly used configuration.

Postman is the most popular tool for testing REST APIs. I guess most developers are familiar with how to use Postman to send various types (GET, POST, PUT, DELETE, etc.) of HTTP requests with various types of payloads (form data, JSON, etc.).

Spring Boot is the most popular tech stack for building Java-based REST APIs. In this tutorial, we will learn how to write tests for Spring Boot applications.

• Create SpringBoot Application
• Unit Testing using JUnit 5 and Mockito
• Integration Testing using TestContainers
• Testing MicroService Integrations using MockServer

In the previous post Kafka Tutorial - Java Producer and Consumer, we learned how to implement a Producer and Consumer for a Kafka topic using the plain Java Client API.

In this post, we are going to look at how to use Spring for Kafka, which provides a high-level abstraction over the Kafka Java Client API to make it easier to work with Kafka.

Kafka, depending on how you use it, can be seen as a Message Broker, Event Store, or a Streaming Platform, etc. Kafka became a preferred technology for many modern applications because of various reasons, like:

• Kafka can be used as an Event Store if you are using an event-driven microservices architecture.
• Kafka can be used as a Message Broker to enable communication across multiple applications.
• Kafka can be used as a streaming platform for processing events in real-time. etc. etc.

I have been working with SpringBoot for many years, and over time, I have worked with many Spring Boot-based codebases. There are a few common mistakes that I observe in projects that use Spring Boot. So, I thought of writing down a few good practices that can be followed while using Spring Boot.