1
0
mirror of https://github.com/H0llyW00dzZ/My-RESTAPIs-Boilerplate.git synced 2025-02-06 09:26:02 +00:00
H0llyW00dzZ 5d698851f7
Update Docs [K8S Deployment] [REST APIs] Deployment Template (#1538)
* Update Docs [K8S Deployment] [REST APIs] Deployment Template

- [+] docs(k8s-deployment): add compatibility notes for attaching external storage in restapis-deploy.yaml

* Update Comments

 [+] docs(restapis-deploy.yaml): update comments for clarity on storage classes and container privileges
2025-01-20 22:10:46 +07:00
..
2024-12-12 05:44:44 +07:00

K8s Deployment for REST API Boilerplate

sailing-with-k8s The-Black-Pearl

This repository provides Kubernetes deployment files for a REST API boilerplate application. The primary focus is on leveraging Kubernetes to address critical infrastructure issues, enabling seamless scaling, and offering freedom from overpaying for licensing or other drama (e.g., bad competitors). Kubernetes allows you to pay primarily for direct hardware resources such as CPU, RAM, and disk, giving you the flexibility and efficiency needed for modern applications.

By utilizing Kubernetes, this deployment can handle billions of requests efficiently through Horizontal Pod Autoscaling (HPA), making it suitable for large-scale applications. The architecture is designed to be stateless, promoting scalability and stability across multiple nodes.

Note

Without Kubernetes, this boilerplate cannot effectively address critical infrastructure issues such as scaling, security, and other (e.g., experimental solutions). It is designed to be stateless because, in Kubernetes, you can separate components instead of combining everything into a single stateful entity. This allows for seamless integration of components like databases and storage.

List Documentation

Redis Insight

This section covers the deployment of Redis Insight.

REST APIs (This Repository)

This section covers the deployment of the REST API boilerplate application.

MySQL

This section covers the deployment of the MySQL database service.


Note

For users in Indonesia (🇮🇩), it's recommended to use the Singapore region instead of Indonesia when creating a cluster with a cloud provider. This is due to the traditional instability of the network in Indonesia (our home), which can lead to issues such as latency and packet loss.