In our previous tutorial, we built a Spring Native microservice using “Bean Validation” to validate Java objects and return i18n messages if the validation fails. Now it’s time to deploy an Amazon Cognito service as an OIDC server to authenticate the users of the City Tasks application. This tutorial is…

In my previous tutorial, I created a Native Spring Boot microservice using TDD with Tescontainers that deploy Postgres and DynamoDB containers to execute the integration tests. The business logic was developed using Spring WebFlux for reactive programming and Quartz to create timed tasks. Now, it’s time to add validations to…

I have already written some tutorials in the past about the Quarkus Framework and the use of Native Executables in a Docker container. Indeed, I have a project called City Tasks in my GitHub organization that is a full-stack application developed with Ionic and Angular in the front-end and Java…

My previous tutorial used TDD with Testcontainers to develop our Timer Service microservice with Spring Boot 3. Now, it’s time to add reactive programming support to our service using WebFlux employing the same TDD approach. So let’s get started. To complete this guide, you’ll need the following tools: Git. AWS…

In previous tutorials, I used the Quarkus Framework to develop and deploy our Tasks Service on AWS (the back-end side). Now, it’s time to give a chance to the new version of the Spring Boot Framework 3, using the same component architecture (Quartz, JPA, and Flyway) as we did before…

Initially, I deployed the Tasks Service API inside the ECS cluster without an AWS Elastic Load Balancer (ELB). Furthermore, each ECS task was registered in the AWS Cloud Map service for later discovery using the AWS API Gateway. The API Gateway was responsible for redirecting all incoming HTTP requests to…

My previous tutorial discussed implementing a Single Sign-On (SSO) using Amazon Cognito as an Identity Provider (IdP) for our Task Service. This service is implemented using the Java/Quarkus Framework for the backend and the Amplify with the Ionic/Angular Framework for the frontend. All these components were implemented in my previous…

So far, we have implemented our Timer Service application using Amplify with Cognito integration for our authentication process. But this component is entirely coupled to our code base, which is a drawback if tomorrow we need to build another app that belongs to our business domain. So it’s better to…

Now, it’s time to automate our Timer Service application’s build and deploy process into AWS. My previous article discussed unit and integration testing using the Quarkus framework employing JUnit and Testcontainers. So now, we’ll automate that process using a CI/CD pipeline using the Amazon Copilot CLI. …