CloudArcade

Guided architecture tour · 6–8 min

Help people find the right words — OpenSearch

Plan a searchable catalog while keeping the main records protected.

This tour teaches architecture decisions. Its services are not provisioned in the emulator.

Your goal

Plan a searchable catalog while keeping the main records protected.

Why this matters

Visitors do not always know an exact product ID. You will build a search copy, choose useful searchable fields, and keep it up to date when products change.

Words you will use

A search index organizes documents for searching. A document is one searchable record. A mapping describes its fields. Indexing means adding or updating a search document.

How to proceed

Read each situation and choose an answer. The lesson explains the result. Try again if needed, then continue through all three decisions and finish the tour.

Play this architecture tour

1. Choose a search copy

Visitors type words such as green hiking bag. The shop still needs its main database for reliable order transactions. Choose a place for a searchable product copy.

What role fits OpenSearch?

Hold a search index of suitable product fields.

OpenSearch supports search and analysis over indexed documents. Keep the main record of important business data where your app expects it. Search results can point back to that record.

The shop adds a search path without confusing it with order storage.

Main product record → search document → search results

2. Choose fields on purpose

Each product has a title, description, price, and private supplier note. People need word search and price filters, but should not see the private note.

What should the index design include?

Suitable field types and only the fields intended for search.

Field choices affect both search quality and exposure. Use text fields for word search and appropriate numeric fields for prices. Leave private details out unless a protected use truly requires them.

The search copy contains useful fields with a clear access boundary.

title: text
price: numeric
private notes: excluded

3. Keep the search copy current

A product is removed from sale, but its old search document remains. A visitor still finds it. Choose a process that keeps the copies aligned.

What should the app maintain?

An update/delete path from main records to the search index.

A search copy needs an update pipeline and a way to repair missed changes. Check the main record before important actions. Finding a product in search does not prove it is still available to buy.

The team can update stale search documents and verify availability.

Main change → index update/delete → monitored retry if needed

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.

Continue with another AWS learning guide