Speed and innovation are crucial to the success of any business. Being able to quickly innovate, test, validate, and rapidly release is key for businesses to stay ahead of their competition. At the same time, it is important to ensure that business-critical services have inbuilt resiliency, performance, and scalability.
Speed and resiliency are two sides of the same coin: Customer confidence in the business. To achieve this confidence, the mission critical services should be built on cloud native principles in combination with site reliability engineering (SRE) principles.
The goals of this post are to examine:
By: Shikha Srivastava, Distinguished Engineer, Master Inventor
Kirti Apte, Senior Software Engineer
A microservices architecture often starts with a focus on only the creation of the backend microservices. This approach can lead to a monolithic UI that combines and surfaces different functions and data from modular backend microservices. These large and complex UIs go against the fundamental concepts of microservice-based architecture, which is to enable multiple microservices to handle their own functions and tasks across both the backend and frontend. With our own application development, we work towards bringing modularity to both the backend and frontend of our applications. …
— Coauthor Hanqiu Zhang
A notable advantage of the microservice architecture is that each team can have full ownership of their services. The teams can design and code the services independent of one another. This also implies that microservices have no control over the applications that use them. Applications that use microservices must have the availability and responsiveness of the microservices. Factor XIII: Observable covered in 7 missing factors from 12-factor application blog talks about using readiness probes to check for readiness of all the dependencies of your application.
Let’s discuss the pattern we established to check for API dependencies.
The 12 factor application provides a well-defined guideline for developing microservices, and is a commonly used pattern to run, scale and deploy applications. In IBM Cloud Private platform, we follow the same 12-Factor application guidelines for developing containerized applications. See Kubernetes & 12-factor apps to learn how we apply and group 12-factor practices, which are supported by the Kubernetes model of container orchestration.
As we reflected on the principles of developing containerized microservices running in Kubernetes, we found that while the 12-factor application guidelines are spot-on, the following 7 factors are equally essential for a production environment: Observable, Schedulable, Upgradable…
IBM Cloud Private, a reliable, scalable, and integrated cloud platform that runs on a customer’s datacenter, is built on open-source, Kubernetes-based container architecture. Learn how you can use the Kubernetes namespace concept to organize your clusters so that you can easily take advantage of common IBM Cloud Private services, like self-service deployment, monitoring, logging, metering and security.
In this blog I will cover:
Typically, enterprises are distributed or organized by departments, geography, line-of-business, or other categories. These groups operate independently, with some layer…