If I'm using a script to populate a database, I can also fine-tune the script as I'm developing my application. I can mess up as much as I want while knowing that when I restart, I get another try. As a developer, there are lots of times when this is a great feature. That may be desirable, especially when you're first developing a solution and want to wipe things out and start all over every time. In the context of Kubernetes, it's ephemeral. There's this small thing: When the pod is destroyed, so is the data. Where? What type? We'll get to that.īack to the subject of a pod's root file system. For now, just know that a volume is a directory somewhere of some type. If you wish to share data with one or more other pods, you'll need to use a volume to store your data, a Kubernetes concept we'll learn more about later. For starters, you can't share data between pods because the file system is local to just that pod. This is perfectly acceptable and works fine. If you are running multiple containers within the same pod, the containers can share the data. If you're running a relational database (RDBMS) or a NoSQL system in a pod-for example, MariaDB or Couchbase-you can use this file system to store your data. That is to say, the file system inside the pod. If you create a pod in Kubernetes, you can use the pod's root file system for storage. Note that when Kubernetes is mentioned, you can assume the information is also applicable to OpenShift. This will give us an understanding from which to start.
We'll start with a broad overview (the buzzword is "30,000-foot view," sigh), then get more detailed in upcoming articles. In this series of articles, we'll take a look at data storage options as they relate to microservices, Kubernetes, and-specifically- Red Hat OpenShift. Go forth and be micro!īut have you noticed that very few are talking about the data part of all this? "Distribute the data, one database per microservice" is the standard, one-size-fits-all (which, at least in clothing, means "one size fits no one") answer. Spread the workload, loosely coupled and written in any mix of software development languages.
If ever there was a hot topic in IT, microservices are "it" right now. The amount of information and number of opinions is staggering, and it can be overwhelming.
Web pages, architectural dissertations, conference talks.
0 kommentar(er)
