Chapter 1: A hands-on walkthrough of building and deploying a full-stack microservices application on k8s, along with supporting framework components — Hello readers, coders, architects … Since I released my book on GraalVM, I have taken a break, from writing. During the break, I have been working on implementing the case study, I covered in the last chapter of the book (Supercharge your applications with GraalVM). …

In this blog, we will walk through the complete process of setting up Vault in the Kubernetes cluster and using Secret Injection to consume the secrets in our Pods. In Chapter 1, we went through the high-level architecture and the design of the Bozobooks.com application. Before we start building our…

In this blog, we will build a quarkus native image application to fetch Book information, by calling Google Books API, and storing the results in the Redis cache for future use. We will also learn how to inject Vault secrets into a quarkus application — In the previous chapter, we configured Vault and stored the Google API key in it. In this chapter, we will build the BozoBookInfoService as a quarkus application and we will be injecting the Google API into it.

Chapter 4: In this blog, we will build the GitOps infrastructure for the project. We will be using GitHub actions for the continuous integration and ArgoCD for deploying the application to the Kubernetes cluster. We will also be integrating the pipeline with Slack, to notify the status. — GitOps Architecture In Chapter 3, we build a Quarkus application, as you would have gone through the build and deploy process, there are a lot of steps, that we need to execute manually. It is always the best practice to automate the build and deployment (Continous Integration/Continous Deployment).

Chapter 5: In this blog, we will build the pipeline to build and deploy the Book Information service that we implemented in Chapter 3. We will be using GitHub Actions for Build and ArgoCD to deploy to our local cluster. — In Chapter 4 we walked through the overall GitOps architecture and approach, Please read that chapter, before u go any further. In that chapter, we also created the base infrastructure.

Chapter 6: In this blog, we will build a Quarkus native image application to store and fetch selected books, by the user. We will be using Panache ORM to access PostgreSQL to store and retrieve the user preferences and will be using PV & PVCs. Book Library Microservice, is called…

Chapter 7: In this blog, we will build a ReactJS application, that will provide UI to search for books, and add them to the personal library. We will be using Firebase for authentication, and Hashicorp Vault to inject some of the secrets. …

Chapter 8: In this blog, we will configure our ingress to use TLS/HTTPS, to access our web application. To generate the certificates we will use Vault, and then to manage certificates we will be using cert-manager Architecture Ingress exposes the services, that we are built to the outside world. It provides…

Chapter 9: Set up the Metrics observability and configure the alert manager to send alerts to our slack channel when something goes wrong. Also, configure Grafana as our single pane of glass. — Observability is one of the very key aspects of distributed application architectures, as it's important for us to get real-time alerts on any failures that may happen in the clusters. It consists of visibility and monitoring of the following

Chapter 10: Configuring Grafana Loki to aggregate all the logs across the Kubernetes cluster and set Grafana alerts to send notifications on Slack — Hey everyone, it’s been more than six months since I got some peaceful time for myself to get back to my series. I have been getting a lot of great feedback and comments from people who have been reading my blogs. Thanks for all your feedback, that is what motivated…