Book Image

The KCNA Book

By : Nigel Poulton
Book Image

The KCNA Book

By: Nigel Poulton

Overview of this book

There is a huge benefit in building small, specialized, single-purpose apps that can self-heal, auto scale, and update regularly without needing downtime. Kubernetes and cloud-native technologies come in handy in building such apps. Possessing the knowledge and skills to leverage Kubernetes can positively enhance possibilities in favor of architects who specialize in cloud-native microservices applications. ‘The KCNA Book’ is designed to help those working in technology with a passion to become certified in the Kubernetes and Cloud-Native Associate Exam. You will learn about containerization, microservices, and cloud-native architecture. You will learn about Kubernetes fundamentals and container orchestration. The book also sheds light on cloud-native application delivery and observability. It focuses on the KCNA exam domains and competencies, which can be applied to the sample test included in the book. Put your knowledge to the test and enhance your skills with the all-encompassing topic coverage. Upon completion, you will begin your journey to get the best roles, projects, and organizations with this exam-oriented book.
Table of Contents (12 chapters)
8: Sample test
Appendix B: Sample Test answers

Monolithic vs microservices

In the past, we built monolithic applications that ran on dedicated physical servers.

Monolithic application is jargon for a large complicated application that does lots of things. For example, a monolithic application may have all of the following services bundled and shipped as a single program.

  • Web front-end
  • Authentication
  • Shopping basket
  • Catalog
  • Persistent store
  • Reporting

The important thing to understand is that all of these services were developed by a single team, shipped as a single program, installed as a single program, and patched and updated as a single program. This meant they were complex and difficult to work with. For example, patching, updating, or scaling the reporting service of a monolithic app meant you had to patch, update, or scale the entire app. This made almost all changes high-risk, often resulting in updates being rolled up into a single very high-risk update performed once a year over a long stressful weekend...