Internet Features   «Prev  Next»

Oracle 26ai Catalog Architecture - Exercise

Design a searchable product catalog

Objective: Assign product data, media storage, web delivery, and access controls to appropriate components in an Oracle AI Database 26ai application.

Background and scenario

House-O-Pets needs a catalog in which customers browse categories, filter products, and view product details, photographs, and downloadable product guides. Employees maintain descriptions, prices, and media. Only approved products and media are visible to customers.

For this exercise, store structured data and media metadata in Oracle AI Database 26ai and the actual media files in OCI Object Storage. Choose either ORDS or a Java application running on WebLogic to provide the catalog API. A browser front end consumes that API and presents the catalog.

Design for growing traffic, protected employee updates, and recoverable content. You are producing a written architecture proposal, not deploying resources or writing a complete application. No download files are required.

Instructions

Submit five numbered answers. Include example schema, table, bucket, object-prefix, API-route, and application-component names where appropriate. The names are your choice. Object prefixes organize object names; they are not operating-system directories or LDAP entries.

  1. Product data: Identify the database tables and their relationships. Explain where product names, prices, categories, publication status, and inventory information belong.
  2. Media and access: Propose a bucket and object naming scheme for images and guides. Explain how customers retrieve approved content and how employee uploads are protected. Account for draft content and expiring access links if you use them.
  3. Application and API delivery: Choose ORDS or a WebLogic-based Java API. Describe the browser-to-API-to-database request path and propose routes for product lists, product details, and categories. Explain how employee changes are authorized.
  4. Metadata and content lifecycle: List useful media metadata fields. Explain how a product refers to its media, how a replacement image becomes visible, and how you handle a failed upload or missing object. Distinguish stable object references from temporary access URLs.
  5. Search, scaling, and recovery: Describe keyword and category search, at least two measures for handling growing traffic, and how both database records and external objects can be recovered. Explain when caching or generated static pages can still be useful.

Exercise scoring

The exercise is worth 10 points, with up to 2 points per numbered answer. Award 1 point for appropriate components or structures and 1 point for explaining their behavior and the relevant operational considerations. Use the reference solution for self-assessment; this page does not automatically grade or execute your design.

Hints

Separate storage, presentation, identity, and authorization. A browser front end still needs a server-side API. Directory products such as OUD do not store the catalog's media files. For this scenario, use object storage as required; database BLOB storage is a valid alternative in other architectures.

Choose features to meet a stated need. Ordinary SQL filters may cover the initial search requirements. Oracle Text or AI Vector Search can be optional extensions with appropriate indexes or embedding models, rather than mandatory components.

Submitting your exercise

Enter all five answers below, then select Submit to view your response alongside one possible solution and the scoring guide.


SEMrush Software 1 SEMrush Banner 1