github/awesome-kubernetes
1
0
Fork 0
mirror of https://github.com/nubenetes/awesome-kubernetes.git synced 2026-08-18 03:46:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Dec 3rd

Browse Source
This commit is contained in:
Inaki Fernandez
2021-12-03 11:08:12 +01:00
parent c2108b7bbb
commit 9aa440e309
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/index.md
+1 -1
View File
@@ -52,7 +52,7 @@ A curated list of awesome references collected since 2018. Microservices archite
- [==How to Explain Kubernetes to a Business Team== 🌟](https://dzone.com/articles/how-to-explain-kubernetes-to-a-business-team)
## Introduction
- [From Java EE To Cloud Native. Microservice Architecture. Openshift VS Kubernetes](introduction.md)
- [Microservice Architecture. From Java EE To Cloud Native. Openshift VS Kubernetes](introduction.md)
- [Microservices FAQ & Kubernetes Native](faq.md)
## SRE Site Reliability Engineering
- [Site Reliability Engineering (SRE)](sre.md)
docs/introduction.md
+2 -2
View File
@@ -1,4 +1,4 @@
# Introduction. From Java EE To Cloud Native. Microservice Architecture. Openshift VS Kubernetes
# Introduction. Microservice Architecture. From Java EE To Cloud Native. Openshift VS Kubernetes
- [Introduction](#introduction)
- [Twelve-Factor Apps in Kubernetes](#twelve-factor-apps-in-kubernetes)
- [Self service developer platform](#self-service-developer-platform)
@@ -253,7 +253,7 @@
## From Java EE To Cloud Native
- [wikipedia: Java Enterprise Edition (Java EE)](https://en.wikipedia.org/wiki/Java_Platform,_Enterprise_Edition)
- [lightbend.com: From Java EE To Cloud Native: The End Of The Heavyweight Era 🌟](https://www.lightbend.com/white-papers-and-reports/java-ee-to-cloud-native-modernization)
- [==lightbend.com: From Java EE To Cloud Native: The End Of The Heavyweight Era== 🌟](https://www.lightbend.com/white-papers-and-reports/java-ee-to-cloud-native-modernization)
## Monolith to Microservices Using the Strangler Pattern
- [dzone: Monolith to Microservices Using the Strangler Pattern 🌟](https://dzone.com/articles/monolith-to-microservices-using-the-strangler-patt) The Strangler Pattern is a popular design pattern to incrementally transform your monolithic application into microservices by replacing a particular functionality with a new service. Once the new functionality is ready, the old component is strangled, the new service is put into use, and the old component is decommissioned altogether.
docs/monitoring.md
+1 -1
View File
@@ -211,7 +211,7 @@ OpenShift Cluster Monitoring components cannot be extended since they are read o
| | __AWS ESS__ | __Elastic Cloud__ | __Self-hosted__ |
| :--- | :--- | :--- | :--- |
| __Operational Burden__ | __Medium__. Requires intimate knowledge of other AWS services to go beyond defaults. | __Low__. Backups, version upgrades, etc. are automated. | __High__ You need to provision, configure and maintain the cluster(s) yourself. |
| __Operational Burden__ | __Medium__. Requires intimate knowledge of other AWS services to go beyond defaults. | __Low__. Backups, version upgrades, etc. are automated. | __High__. You need to provision, configure and maintain the cluster(s) yourself. |
| __Cost__ | __Medium__. Over 50% premium on underlying infrastructure cost. | __High__. Up to 3x the cost of underlying infrastructure.| __Low__. Only pay for the underlying infrastructure. Optionally can purchase x-pack license for additional features and support. |
| __Configurability__ | __Low__. No support for custom plugins. Several configuration parameters are not available. | __Medium__. Does support custom plugins and all parameters are available. Lack of direct node ssh access. | __High__. Full node-level acess. |
| __Monitoring__ | __Mediocre__. Kibana monitoring is not available. Cloudwatch is often inadequate for Elasticsearch monitoring. | __Good__. Kibana monitoring available and pre-installed. | __Depends__. It is up to you to implement an adequate monitoring system, but you have access to kibana monitoring. |