```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());

 * This factory maintains a registry of data store implementations and provides methods
 * to register, retrieve, and discover available data stores.
 *
 * <p>Data stores are registered by name and class name, allowing flexible lookup.
 * The factory also supports dynamic discovery of data store plugins by scanning
 * JAR files for data store configurations.</p>
 *

        // Add some info to map
        crawlingInfoHelper.putToInfoMap("url_count", "100");
        crawlingInfoHelper.putToInfoMap("error_count", "5");

        // Store with create=true
        crawlingInfoHelper.store(sessionId, true);

        // Verify infoMap is cleared
        assertNull(crawlingInfoHelper.infoMap);
    }

    public void test_store_existing() {

      val server = field.get(null) as? MockWebServer ?: continue

      // Put the instance in the store, so JUnit closes it for us in afterAll.
      store.put(field, server)

      server.start()
    }
  }

  override fun beforeEach(context: ExtensionContext) {
    val testInstance = context.testInstance.get()
    val store = context.getStore(Namespace.create(StartStop::class.java))

    val instanceFields =

        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"));

     * @param comments
     *            Comments.
     */
    public static void store(final Properties props, final OutputStream out, final String comments) {
        assertArgumentNotNull("props", props);
        assertArgumentNotNull("out", out);

        try {
            props.store(out, comments);
        } catch (final IOException e) {
            throw new IORuntimeException(e);
        }