As we discussed in the previous section, we can enforce ORASTAR rules through a control and data plane. Let's go over these concepts in a bit more detail:

• Control plane: You can use this to push down configurations, policies, and management services to a data plane for controlling routing, traffic, monitoring, discovery, and registration of services. The control plane is responsible for establishing communication between microservices through authentication, authorization, and securing network traffic.
• Data plane: All of the sidecars of the microservices form the data plane. The control and data plane, when used together, form the service mesh:

In the preceding diagram, the control plane interacts with the data plane to manage the service mesh's outcome. Its core responsibility is to translate, enforce, and forward service traffic from every service instance and analyze network traffic in parallel.