ProtectedconstructorProtectedBaseAll component records bulk-loaded from the database, including heavy columns (Specification, vectors, prose fields). Only available server-side.
StaticInstanceInitializes the engine. Configures the base ComponentMetadataEngine and bulk-loads the Components array for server-side use.
OptionalforceRefresh: booleanOptionalcontextUser: UserInfoOptionalprovider: IMetadataProviderFinds a component by name (case-insensitive), optionally filtered by namespace and registry. Uses the in-memory Components array for instant lookups.
Optionalnamespace: stringOptionalregistry: stringFinds a component by its primary key ID using the in-memory Components array.
The Global Object Store is a place to store global objects that need to be shared across the application. Depending on the execution environment, this could be the window object in a browser, or the global object in a node environment, or something else in other contexts. The key here is that in some cases static variables are not truly shared because it is possible that a given class might have copies of its code in multiple paths in a deployed application. This approach ensures that no matter how many code copies might exist, there is only one instance of the object in question by using the Global Object Store.
Protected StaticgetReturns the singleton instance of the class. If the instance does not exist, it is created and stored in the Global Object Store. If className is provided it will be used as part of the key in the Global Object Store, otherwise the actual class name will be used. NOTE: the class name used by default is the lowest level of the object hierarchy, so if you have a class that extends another class, the lowest level class name will be used.
OptionalclassName: string
Server-side Component Metadata Engine that wraps ComponentMetadataEngine and adds the bulk-loaded Components array for server-only use cases like vector search, embedding generation, and full-catalog operations.
Uses composition (containment) rather than inheritance to avoid duplicate data loading. Delegates all base functionality to ComponentMetadataEngine.Instance while adding the
Componentsproperty that bulk-loads all component records.The base ComponentMetadataEngine intentionally does NOT load
MJ: Componentsbecause the entity contains ~150+ MB of nvarchar(MAX) data (Specification, vectors, prose fields) that would poison the browser-side cache and cause 20+ second cold loads. This server class makes that data available where it's needed (e.g., Skip-Brain's SkipComponentEngine) without impacting client-side performance.Follows the same pattern as AIEngine containing AIEngineBase and QueryEngineServer containing QueryEngine.
Description
ONLY USE ON SERVER-SIDE. For metadata only, use the ComponentMetadataEngine class which can be used anywhere.