add isolation concept and move service meshes

Signed-off-by: Hannah Hunter <hannahhunter@microsoft.com>

daprdocs/content/en/concepts/faq.md

@@ -1,42 +0,0 @@
----
-type: docs
-title: "Frequently asked questions and answers"
-linkTitle: "FAQs"
-weight: 1000
-description: "Common questions asked about Dapr"
----
-
-## How does Dapr compare to service meshes such as Istio, Linkerd or OSM?
-Dapr is not a service mesh. While service meshes focus on fine-grained network control, Dapr is focused on helping developers build distributed applications. Both Dapr and service meshes use the sidecar pattern and run alongside the application. They do have some overlapping features, but also offer unique benefits. For more information please read the [Dapr & service meshes]({{<ref service-mesh>}}) concept page.
-
-## Performance Benchmarks
-The Dapr project is focused on performance due to the inherent discussion of Dapr being a sidecar to your application. See [here]({{< ref perf-service-invocation.md >}}) for updated performance numbers.
-
-## Actors
-
-### What is the relationship between Dapr, Orleans and Service Fabric Reliable Actors?
-
-The actors in Dapr are based on the same virtual actor concept that [Orleans](https://www.microsoft.com/research/project/orleans-virtual-actors/) started, meaning that they are activated when called and deactivated after a period of time. If you are familiar with Orleans, Dapr C# actors will be familiar. Dapr C# actors are based on [Service Fabric Reliable Actors](https://docs.microsoft.com/azure/service-fabric/service-fabric-reliable-actors-introduction) (which also came from Orleans) and enable you to take Reliable Actors in Service Fabric and migrate them to other hosting platforms such as Kubernetes or other on-premises environments.
-Moreover, Dapr is about more than just actors. It provides you with a set of best-practice building blocks to build into any microservices application. See [Dapr overview]({{< ref overview.md >}}).
-
-### Differences between Dapr and an actor framework
-
-Virtual actor capabilities are one of the building blocks that Dapr provides in its runtime. With Dapr, because it is programming-language agnostic with an http/gRPC API, the actors can be called from any language. This allows actors written in one language to invoke actors written in a different language.
-
-Creating a new actor follows a local call like `http://localhost:3500/v1.0/actors/<actorType>/<actorId>/…`. For example, `http://localhost:3500/v1.0/actors/myactor/50/method/getData` calls the `getData` method on the newly created `myactor` with id `50`.
-
-The Dapr runtime SDKs have language-specific actor frameworks. For example, the .NET SDK has C# actors. The goal is for all the Dapr language SDKs to have an actor framework. Currently .NET, Java, Go and Python SDK have actor frameworks.
-
-### Does Dapr have any SDKs I can use if I want to work with a particular programming language or framework?
-
-To make using Dapr more natural for different languages, it includes [language specific SDKs]({{<ref sdks>}}) for Go, Java, JavaScript, .NET,  Python, PHP, Rust and C++. These SDKs expose the functionality in the Dapr building blocks, such as saving state, publishing an event or creating an actor, through a typed language API rather than calling the http/gRPC API. This enables you to write a combination of stateless and stateful functions and actors all in the language of your choice. And because these SDKs share the Dapr runtime, you get cross-language actor and functions support.
-
-### What frameworks does Dapr integrate with?
-Dapr can be integrated with any developer framework. For example, in the Dapr .NET SDK you can find ASP.NET Core integration, which brings stateful routing controllers that respond to pub/sub events from other services.
-
-Dapr is integrated with the following frameworks;
-
-- Functions with Dapr [Azure Functions Extension](https://github.com/dapr/azure-functions-extension)
-- Spring Boot Web apps in Java SDK
-- ASP.NET Core in .NET SDK
-- [Azure API Management](https://cloudblogs.microsoft.com/opensource/2020/09/22/announcing-dapr-integration-azure-api-management-service-apim/)

daprdocs/content/en/concepts/faq/_index.md

@@ -0,0 +1,7 @@
+---
+type: docs
+title: "Frequently asked questions and answers"
+linkTitle: "FAQs"
+weight: 10
+description: "Learn more about Dapr concepts through frequently asked questions"
+---

daprdocs/content/en/concepts/faq/service-mesh.md

@@ -2,7 +2,7 @@
 type: docs
 title: "Dapr and service meshes"
 linkTitle: "Service meshes"
-weight: 900
+weight: 200
 description: >
   How Dapr compares to and works with service meshes
 ---

daprdocs/content/en/concepts/isolation-concept.md

@@ -0,0 +1,41 @@
+---
+type: docs
+title: "Isolation"
+linkTitle: "Isolation"
+weight: 700
+description: How Dapr provides namespacing and isolation
+---
+
+Dapr namespacing provides isolation and multi-tenancy. Dapr supports namespaced service invocation, components, pub/sub, and actors in both self-hosted mode and on Kubernetes. 
+
+To get started, create and configure your namespace.
+
+{{< tabs "Self-Hosted" "Kubernetes">}}
+
+{{% codetab %}}
+
+In self-hosted mode, specify the namespace for a Dapr instance by setting the `NAMESPACE` environment variable.
+
+{{% /codetab %}}
+
+{{% codetab %}}
+
+On Kubernetes, create and configure the namespace:
+
+```bash
+kubectl create namespace namespaceA
+kubectl config set-context --current --namespace=namespaceA
+```
+
+Then deploy your applications into this namespace.
+
+{{% /codetab %}}
+
+{{< /tabs >}}
+
+Learn how to use namespacing throughout Dapr:
+
+- [Service Invocation namespaces]({{< ref service-invocation-namespaces.md >}})
+- [Scope pub/sub topic access]({{< ref pubsub-scopes.md >}})
+- [Scope components to one or more applications]({{< ref component-scopes.md >}})
+- [Namespaced actors](todo)

daprdocs/content/en/concepts/terminology.md

@@ -2,7 +2,7 @@
 type: docs
 title: "Dapr terminology and definitions"
 linkTitle: "Terminology"
-weight: 900
+weight: 1000
 description: Definitions for common terms and acronyms in the Dapr documentation
 ---