In this post, i have updated my old microservices app and explained the changes. It is now working in Spring Framework 2024 specs.
In this post, i have explained how to create a demo blog application with up-to-date Spring Boot MVC in 1 day.
In this post, i have prepared and explained tech mix of projects from JavaFX, OpenCV, Jakarta, Hibernate, Thymeleaf, Spring Framework and Spring Security. They use the latest libraries and they actually work as of January 2024. I have also explained why i have bothered myself to prepare these projects.
Even though web development nowadays are hugely shifted towards spring boot and thymeleaf or javascript frameworks, there are still projects or knowledges out there that uses spring framework and JSP. I have prepared a base project for those who want to rewrite their old projects in 2022 standards, while using spring framework and most common ORM tool, hibernate.
Lately i have realized the potential of the specification API of the spring framework together with the JpaRepositories. In this post, i will give you a brief and working restful service implementation with spring data jpa.
In this last post of series about RabbitMQ and its integration into a microservice architecture, we will analyze our decisions and implementations. We will also try to figure out possible problems and solutions.
In this post, we will receive the messages that we have sent to rabbit by listening to the queues. We will add a small mailing service to the system.
In this post, we will send messages from mciroservice MVC application to RabbitMQ using Spring AMQP. We will also see the management console and the state of the queues and messages.
It is time to get to know RabbitMQ that we integrate in our microservice application more in depth.
In this series, we will add new functionalities with RabbitMQ on top of the SAGA based microservice application. We will also understand and analyze message broker tools.
Now it is time to look back. In this post, i will try to analyze the application i have designed with microservice architecture with ups and downs. What could be our gains, losses or alternatives?
We have coded all the necessary services in this series of posts. It is time to run the microservice system. We have 11 projects and we will see how to deploy and run them with a single click, without a management tool.
In this post, we will write a consumer MVC web app for our microservices. It will be the SAGA orchestrator. This project will complete the big picture.
We have analyzed our application and introduced the tools in this SAGA based microservice series. We have coded and run the backbone of the system in the last post. In this post, we will understand how to add new small services on top of this system and start 1 of them.
We will code and launch 3 project of the backbone system of our SAGA based microservice architecture. Eureka, Config Server and Gateway.
We will continue analyzing and building our SAGA microservice architecture. The last post was the introduction. In this post, we will take a look at the backbone system.
In this post, we will dive into the famous microservices world by developing a simple application. You will be able to run your own microservice application by following this 7 part blog post. Let the journey begin.
With a little bit experince, you can actually create a website like this within 2-3 days. I think coding this website can be easier than sturggling with wordpress and php and you might also save money by not using premium tools.