# Bootstraping

To get started fast ask yourself the following questions **how strategic is what i build?** and **how much need for change exists?**:&#x20;

![](https://412027953-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LBulIh9Wa6TPIk4F7x5%2F-LBur3CGk77DNujjr9mU%2F-LBusX6bfaFBtkVk5hjW%2Fserverless-vs-containers.png?alt=media\&token=6fb3a24a-da93-44f1-a86a-e8648a5cb16d)

## Backend / APIs:

* When I have a small *on demand* (I don't expect at least 1 user per hour on average) function I use serverless: [Serverless Starter](https://den.gitbook.io/developerplaybook/bootstraping)&#x20;
* When I have *always on* (e.g. polling function or expect more then 1 user per hour) then I use docker: [docker-starter](https://github.com/denseidel/docker-starter)&#x20;
* When I expect to have applications that require more then 2 nodes (e.g. 6+ applications) then I use the kubernetes/istio with [service-mesh-starter](https://github.com/denseidel/cloud-setup)

## Frontend:

* Setup a Frontend (including auth and my component library): [spa-starter](https://github.com/denseidel/spa-starter)

Analytics Pipeline:

* Setup a Data Architecture (Object Store + Training Pipeline + Models as a Service): [Analytics Starter](https://den.gitbook.io/developerplaybook/bootstraping)
