Today we continue discussing the best practice from storage engineering:
401) Catalog can be maintained as a one stop shop in a store. There does not need to be sub-catalogs or fragmentation or ETL or MessageBus
402) Catalogs can remain equally available to Application servers, API data and services and webservers.
403) Catalogs can also be made available behind the store for supply chain management and data warehouse analytics
404) Catalogs can be made available for browsing as well as searching via such facilitators as Lucene search index
405) Catalogs can support geo-sharding with persisted shard ids or more granular store ids for improving high availability
406) Catalogs support data modeling, data synchronization, data standardization, and flexible workflows. There are layer of information management using catalog starting with print/translation workflows at the bottom layer, followed by workflow or security for access to the assets, their editing, insertions and bulk insertions, followed by integrations or portals followed by flexible integration capabilities, full/data exports, multiple exports, followed by integration portals for integration with imports/exports, data pools and platforms, followed by digital asset management layer for asset on-boarding and delivery to channels, and lastly data management for searches, saved searches, channel based content, or localized content and the ability to author variants, categories, attributes and relationships to stored assets.
401) Catalog can be maintained as a one stop shop in a store. There does not need to be sub-catalogs or fragmentation or ETL or MessageBus
402) Catalogs can remain equally available to Application servers, API data and services and webservers.
403) Catalogs can also be made available behind the store for supply chain management and data warehouse analytics
404) Catalogs can be made available for browsing as well as searching via such facilitators as Lucene search index
405) Catalogs can support geo-sharding with persisted shard ids or more granular store ids for improving high availability
406) Catalogs support data modeling, data synchronization, data standardization, and flexible workflows. There are layer of information management using catalog starting with print/translation workflows at the bottom layer, followed by workflow or security for access to the assets, their editing, insertions and bulk insertions, followed by integrations or portals followed by flexible integration capabilities, full/data exports, multiple exports, followed by integration portals for integration with imports/exports, data pools and platforms, followed by digital asset management layer for asset on-boarding and delivery to channels, and lastly data management for searches, saved searches, channel based content, or localized content and the ability to author variants, categories, attributes and relationships to stored assets.
No comments:
Post a Comment