The Turbonomic Market is an abstraction that represents the datacenter as buyers and sellers in a supply chain. Each entity (such as physical machines, virtual machines, storage device, volume, application component) in the environment is a buyer or seller.  The Turbonomic Supply Chain is a graphical display of the buyer and seller relationships. 

Turbonomic uses Virtual Currency to give a budget to buyers and assign cost to resources. This virtual currency assigns value across all tiers of your environment, making it possible to compare the cost of application transactions with the cost of space on a disk or physical space in a datacenter.

[Also called Cloud-Native] Microservice architecture  is a method of developing software applications as a suite of independently deployable, small, modular services in which each service runs a unique process and communicates  a well-defined lightweight mechanism to serve a business goal. 

Starting in Version 7.0, Turbonomic has been architected as a microservice. 

A Namespace in computer science (sometimes also called a name scope) is an abstract container or environment created to hold a logical grouping of unique identifiers or symbols (i.e., names). An identifier defined in a namespace is associated only with that namespace.(Wikipedia: https://en.wikipedia.org/wiki/Namespace#:~:text=A%20namespace%20in%20computer%20science,associated%20only%20with%20that%20namespace.)

A Kubernetes Namespace is a logical pool of resources in a Kubernetes environment that manages workloads based on specific requirements or business needs. For example, administrators can pool resources for different organizations within the enterprise and assign different policies to each pool.

A Namespace Entity is the Turbonomic Supply Chain entity that represents a Kubernetes Namespace. See also Namespace (Kubernetes). 

Turbonomic treats quotas defined in namespaces as constraints when making sizing decisions for containers. When you scope to a Namespace Entity in the supply chain, the Capacity and Usage chart shows Capacity values as namespace quotas.

The Turbonomic Navigation Bar is a menu of key Turbonomic pages and other resources including notifications (from the Notification Center), the Green Circle, Help, and Feedback. 

The Navigation Bar appears on the left side of the Turbonomic user interface.

New Relic One is an observability platform built to help engineers create software. It is designed to instrument, analyze, troubleshoot, and optimize your entire software stack.

Turbonomic supports discovery of the application infrastructure monitored by New Relic, and can make recommendations and take actions to both assure performance and drive efficiency with the full knowledge of the demands of each individual application experience.

For a Reserved Instance (RI) in AWS environments, nfu is a measure of RI capacity that you can use to compare or combine that capacity for different template families. For AWS environments, Turbonomic measures RI utilization and coverage in terms of nfu.

Measuring by nfu gives a common measure for RI capacity across different instance families.  For example, assume ts_small factors to 1 nfu, while ts_large factors to 4 nfu. If you reserve one small and one large workload, your RI consumption is 5 nfu.

See also RI Ratio for Azure environments

A NIC (Network Interface Card) provides a dedicated network connection to the computer it’s installed on.  Without it, a computer could not connect to a network. It can be used in both wired and wireless communications, providing both a physical layer and data link layer device. 

When scaling cloud workloads, Turbonomic uses maximum supported NICs as a property of an instance type, and recommends the cheapest instance type that will meet a workload’s demand.