Chill+, a video streaming platform, is becoming increasingly popular. To support its success, the company is scaling out its Kubernetes cluster. As a result, Chill+’s infrastructure costs are skyrocketing. Your task as a software engineer is to devise strategies for managing these costs by reducing resource consumption. Leveraging the OpenID Connect (OIDC) protocol, you’ll increase security by adding an authentication and authorization layer. To improve observability, you’ll add probes, metrics, logs, and tracing to Chill+’s Catalog API. You’ll implement fault-tolerance strategies, and you’ll provide crucial (HTTP-based and asynchronous Kafka-based) inter-service communication. When you’re finished with these liveProjects, you’ll have practical experience reducing Kubernetes microservice resource consumption as well as valuable skills for managing infrastructure costs.
Those new to Quarkus should try A Microservice with Quarkus and Kubernetes first.
Now I am fairly comfortable with Quarkus (coming from a Spring Boot background). I am ready to use it in my new project at work.
You’re a software engineer at Chill+, a video streaming platform that uses Java to develop its microservice architecture running on Kubernetes. Thanks to the company’s soaring popularity, Chill+ is scaling out its Kubernetes cluster. Your task is to reduce infrastructure costs, which are growing faster than the company’s customer base. To achieve your goal, you’ll add security that reduces resource consumption. You’ll implement an authentication layer, integrated with developer-friendly Quarkus Keycloak, on the company’s Catalog API. You’ll restrict access to the API’s endpoint according to users’ roles, tune the Keycloak Dev Services to match the Catalog’s API context, and verify the security implementation leveraging Quarkus’s easy-to-use testing libraries.
Chill+, a video streaming platform, is becoming increasingly popular. To support its success, the company, which uses Java to develop its microservice architecture, is scaling out its Kubernetes cluster. As a software engineer, your task is to take control of the company’s skyrocketing infrastructure costs, and your solution is to reduce resource consumption by increasing observability. You’ll configure Chill+’s Catalog API log using Quarkus’ built-in logging capabilities, add default Quarkus healthiness and readiness probes, and use Micrometer, a JVM-based metrics instrumentation library, to expose the API’s performance and export those metrics to Prometheus and Grafana. When you’re done, you’ll have provided a level of observability that will help Chill+ monitor and reduce resource consumption, significantly decreasing infrastructure costs.
The success of Chill+ is soaring, but so are its infrastructure costs. As a software engineer for this nextgen video streaming platform, it’s up to you to devise a cost-mitigating plan. Your solution is to reduce resource consumption by implementing crucial interservice communication and fault tolerance. You’ll use a REST client to integrate with another HTTP service, mock external calls with Mockito, and run tests against a mock HTTP server using a fixture. You’ll use the Quarkus Fault Tolerance extension to incorporate resiliency patterns, and you’ll implement error handling by adding retries, timeouts, circuit breakers, and fallbacks to the Catalog API. When you’re done, Chill+’s catalog service will return more accurate results to its customers with fewer requests, and have increased—and less costly—fault resilience.
Enter course descriptionChill+, the nextgen streaming platform you work for, is scaling out its Kubernetes cluster to meet the demands of its increasing popularity. As a software engineer, your job is to devise a plan for managing the company’s infrastructure costs which are rising as fast as its success. Your solution is to reduce resource consumption by implementing crucial interservice communication. To make this communication asynchronous, which provides the benefit of decoupled request/response temporality while improving communication performance, you’ll use a Kafka producer to integrate with another service, and you’ll use Quarkus SmallRye Reactive Messaging Kafka Connector to produce and consume data. When you’re done, Chill+’s catalog service will provide quicker, more accurate recommendations to its customers while decreasing Chill+’s infrastructure costs.
I had not known anything about Quarkus before and learned in a short time.
Excellent liveProject. Very useful technique to apply in real life projects.
These liveProjects are for software engineers with knowledge of OpenId Connect and experience building Java applications. To begin these liveProjects you’ll need to be familiar with the following:TOOLS
In this liveProject series, you’ll learn to leverage Quarkus to implement security, observability, and interservice communication—skills that have real-world value for reducing microservice resource consumption and managing infrastructure costs.
geekle is based on a wordle clone.