```mermaid
flowchart LR
    subgraph global[global env]
        harry-1[harry v1]
    end
    subgraph stone-project[philosophers-stone project]
        stone(philosophers-stone) -->|requires| harry-1
    end
```

  - login: olexkram
    avatarUrl: https://avatars.githubusercontent.com/u/148793576?v=4
    url: https://github.com/olexkram
  - login: 0ne-stone
    avatarUrl: https://avatars.githubusercontent.com/u/62360849?u=746dd21c34e7e06eefb11b03e8bb01aaae3c2a4f&v=4
    url: https://github.com/0ne-stone
  - login: nayasinghania
    avatarUrl: https://avatars.githubusercontent.com/u/74111380?u=752e99a5e139389fdc0a0677122adc08438eb076&v=4

Then you could want to have **a single container** with a **process manager** starting **several worker processes** inside.

---

The main point is, **none** of these are **rules written in stone** that you have to blindly follow. You can use these ideas to **evaluate your own use case** and decide what is the best approach for your system, checking out how to manage the concepts of:

* Security - HTTPS
* Running on startup

                commitCount.incrementAndGet();
            }
        };

        // Store some documents
        DataStoreParams params = new DataStoreParams();
        Map<String, Object> data = new HashMap<>();

        callback.store(params, data);
        callback.store(params, data);
        callback.store(params, data);

        assertEquals(3L, callback.getDocumentSize());

        params.put("key1", "value1");
        params.put("key2", "value2");

        IndexUpdateCallback callback = new TestIndexUpdateCallback();

        // Execute store method
        dataStore.store(config, callback, params);

        // Verify store was called
        assertTrue(storeCalled.get());
        assertNotNull(capturedConfig.get());
        assertEquals("test-config", capturedConfig.get().getName());

        dataMap.put("title", "Test Document");

        // Execute
        indexUpdateCallback.store(paramMap, dataMap);

        // Verify
        assertEquals(1, indexUpdateCallback.getDocumentSize());
        // Check if fields were added (they should be added by the store method)
        assertNotNull("ID should be set", dataMap.get("id"));

        }

    }

    /**
     * Inner thread class for executing data store crawling operations.
     * Each thread handles crawling for a single data configuration,
     * processing documents and updating the search index.
     *
     * <p>The thread manages:</p>
     * <ul>
     *   <li>Data store initialization and document processing</li>
     *   <li>Index update operations through callbacks</li>

     * @param create if true, creates a new crawling info regardless of existing records
     * @throws FessSystemException if unable to store the crawling session
     */
    public synchronized void store(final String sessionId, final boolean create) {
        CrawlingInfo crawlingInfo = create ? null : getCrawlingInfoService().getLast(sessionId);
        if (crawlingInfo == null) {

        return getKuromojiFile(dictId).map(file -> file.get(id).get());
    }

    /**
     * Store a Kuromoji item.
     *
     * @param dictId The dictionary ID.
     * @param kuromojiItem The Kuromoji item to store.
     */
    public void store(final String dictId, final KuromojiItem kuromojiItem) {
        getKuromojiFile(dictId).ifPresent(file -> {

import org.codelibs.fess.unit.UnitFessTestCase;

public class DataStoreExceptionTest extends UnitFessTestCase {

    public void test_constructor_withMessage() {
        // Test with message only
        String message = "Data store error occurred";
        DataStoreException exception = new DataStoreException(message);

        assertNotNull(exception);
        assertEquals(message, exception.getMessage());
        assertNull(exception.getCause());