From the list of deployment concepts from above, using workers would mainly help with the **replication** part, and a little bit with the **restarts**, but you still need to take care of the others:

* **Security - HTTPS**
* **Running on startup**
* ***Restarts***
* Replication (the number of processes running)
* **Memory**
* **Previous steps before starting**

## Containers and Docker { #containers-and-docker }

* Docker in Swarm Mode
* Systemd
* Supervisor
* Handled internally by a cloud provider as part of their services
* Others...

I'll give you more concrete examples in the next chapters.

## Restarts { #restarts }

Similar to making sure your application is run on startup, you probably also want to make sure it is **restarted** after failures.

### We Make Mistakes { #we-make-mistakes }

## Running on Startup and Restarts { #running-on-startup-and-restarts }

There is normally another tool in charge of **starting and running** your container.

It could be **Docker** directly, **Docker Compose**, **Kubernetes**, a **cloud service**, etc.

The cache directory must be exclusively owned by a single instance.

Deleting the cache when it is no longer needed can be done.  However this may delete the purpose of the cache
which is designed to persist between app restarts.

```kotlin
cache.delete()
```

## Pruning the Cache

Pruning the entire Cache to clear space temporarily can be done using evictAll.

```kotlin
cache.evictAll()
```

This is the basic idea. But you will probably want to take care of some additional things, like:

* Security - HTTPS
* Running on startup
* Restarts
* Replication (the number of processes running)
* Memory
* Previous steps before starting

        pythonJob.arg("arg2");
        assertEquals(2, pythonJob.argList.size());
        assertEquals("arg2", pythonJob.argList.get(1));
    }

    // Test multiple arguments addition
    @Test
    public void test_args() {
        assertTrue(pythonJob.argList.isEmpty());

        PythonJob result = pythonJob.args("arg1", "arg2", "arg3");

        assertSame(pythonJob, result);
        assertEquals(3, pythonJob.argList.size());

* Systemd
* Supervisor
* Bir cloud provider tarafından servislerinin parçası olarak içeride yönetilmesi
* Diğerleri...

Sonraki bölümlerde daha somut örnekler vereceğim.

## Yeniden Başlatmalar { #restarts }

Uygulamanızın startup'ta çalıştığından emin olmaya benzer şekilde, hatalardan sonra **yeniden başlatıldığından** da emin olmak istersiniz.

### Hata Yaparız { #we-make-mistakes }

* Docker в режиме Swarm (Swarm Mode)
* Systemd
* Supervisor
* Обработка внутри облачного провайдера как часть его услуг
* Прочие...

Более конкретные примеры будут в следующих главах.

## Перезапуски { #restarts }

Подобно тому как вы обеспечиваете запуск приложения при старте, вы, вероятно, захотите обеспечить его **перезапуск** после сбоев.

### Мы ошибаемся { #we-make-mistakes }

- Docker у режимі Swarm
- Systemd
- Supervisor
- Обробляється внутрішньо хмарним провайдером як частина їхніх сервісів
- Інші...

У наступних розділах я наведу більш конкретні приклади.

## Перезапуски { #restarts }

Подібно до забезпечення запуску застосунку під час старту системи, ви, ймовірно, також захочете гарантувати його **перезапуск** після збоїв.

### Ми помиляємося { #we-make-mistakes }

* Systemd
* Supervisor
* Manejado internamente por un proveedor de nube como parte de sus servicios
* Otros...

Te daré más ejemplos concretos en los próximos capítulos.

## Reinicios { #restarts }

De manera similar a asegurarte de que tu aplicación se ejecute al iniciar, probablemente también quieras asegurarte de que se **reinicie** después de fallos.

### Cometemos Errores { #we-make-mistakes }