Cloud Native Development Design Patterns

Cloud Native Development Design Patterns

5bc984d78def65048378c439d77c379f?s=128

Tomoya Amachi

May 20, 2020
Tweet

Transcript

  1. 6.
  2. 7.

    Others Kubernetes We will use Multi-services Monolithic My applications are

    Master I am a cloud native Beginner I want to develop like a production environment Mirror accept another environment Dependency services are * if you use datasources shared with member on my own
  3. 10.

    ➔ No need to learn about Kubernetes, using Docker API

    ➔ Easy to understand for beginners (less configurations) ➔ It is not suited for production https://docs.docker.com/compose/ Others Kubernetes Multi-services Monolithic Master Beginner Mirror accept another environment shared with member on my own
  4. 11.

    ➔ Local process proxy to remote Kubernetes ➔ Developers do

    not need to know about containers ➔ Must be careful not to override another developer’s service https://www.telepresence.io/ Others Kubernetes Multi-services Monolithic Master Beginner Mirror accept another environment shared with member on my own
  5. 12.

    ➔ Rebuild images and deploy to (your) Kubernetes cluster ➔

    Slow process if a container image is big ➔ If you want to use a remote cluster, built images should be sent to an image registry https://skaffold.dev/ Others Kubernetes Multi-services Monolithic Master Beginner Mirror accept another environment shared with member on my own
  6. 13.

    ➔ Necessary to be able to write Tiltfile, like shell

    script ➔ Send changed files to containers, then run script in containers ➔ Rich UI and be able to check errors in multi-service easily https://tilt.dev/ Others Kubernetes Multi-services Monolithic Master Beginner Mirror accept another environment shared with member on my own