Java, Spring Boot, Microservices, Cloud and DevOps Tutorials
In MicroServices using Spring Boot & Spring Cloud – Part 1: Overview, we took a brief look at what microservices are and how we can use Spring Boot and Spring Cloud to build them.
In this post, we are going to learn:
Nowadays, “MicroServices” is the hot buzzword in software development, and many organizations prefer building their enterprise applications using a MicroServices architecture. In the Java community, Spring Boot is the most widely used framework for building both monoliths and microservices. I am planning to write a series of articles covering how to build microservices using Spring Boot and Spring Cloud.
Spring Boot is the most popular and widely used Java framework. This discussion of “Why is Spring Boot so popular?” occasionally comes up between me and my friends/colleagues. Also, I get emails from various people asking, “Spring is huge; how can I learn it quickly?”. In this post, I will try to answer these two questions.
RabbitMQ is one of the most popular message broker solutions and provides client libraries to be used from various programming languages, including Java, Scala, .NET, Go, Python, Ruby, PHP, etc. In this tutorial, we will learn how to use the RabbitMQ message broker to send and receive messages from a Spring Boot application. We will also look at how to send messages as JSON payloads and how to deal with errors using Dead Letter Queues (DLQ).
In web applications, user session management is very crucial for managing user state. In this article, we are going to learn about the approaches we have been following to manage user sessions in a clustered environment and how we can use Spring Session to implement it in a much simpler and more scalable way.
In this article, we are going to learn how we can use Travis CI for Continuous Integration and Continuous Deployment (CI/CD) of a Spring Boot application. We will learn how to run Maven build goals, perform test coverage validation using the JaCoCo plugin, run Code Quality checks using SonarCloud, build a Docker image and push it to DockerHub, and finally deploy it to Heroku.
In the previous article, Introduction to Spring Cloud Config Server, we have seen how to use Spring Cloud Config Server.
But the problem is that to reload the config changes in Config Client applications, we need to trigger the /refresh endpoint manually. This is not practical or viable if you have a large number of applications.
Spring Boot provides a lot of flexibility in externalizing configuration properties via properties or YAML files. We can also configure properties for each environment (dev, qa, prod, etc.) separately using profile-specific configuration files such as application.properties, application-dev.properties, application-prod.properties, etc. But once the application is started, we cannot update the properties at runtime. If we change the properties, we need to restart the application to use the updated configuration properties.
We can use IntelliJ IDEA Community Edition for working with Spring Boot applications, as we don’t need support for configuring servers like Tomcat, Wildfly, etc., and can simply run the applications by running the main() method.
However, there is no provision in IntelliJ IDEA Community Edition to create a Spring Boot application directly, the way it is supported in the Ultimate Edition.
I would like to let you know that I have updated/added the following sections to my SpringBoot: Learn By Example book.
