https://github.com/deirofelippe/frontend-appvideos

Cadastro de usuarios com: Nodejs, React, Testes automatizados Docker Compose, Kubernetes, Elastic APM, Cache com Redis, Apache Kafka, SonarQube, GitHub Actions.
https://github.com/deirofelippe/frontend-appvideos

apache-kafka docker-compose elastic-apm github-actions kubernetes nodejs react redis sonarqube test

Last synced: 23 days ago
JSON representation

Cadastro de usuarios com: Nodejs, React, Testes automatizados Docker Compose, Kubernetes, Elastic APM, Cache com Redis, Apache Kafka, SonarQube, GitHub Actions.

• Host: GitHub
• URL: https://github.com/deirofelippe/frontend-appvideos
• Owner: deirofelippe
• Created: 2022-01-24T23:10:01.000Z (almost 3 years ago)
• Default Branch: main
• Last Pushed: 2022-02-26T11:06:53.000Z (almost 3 years ago)
• Last Synced: 2023-03-06T11:32:31.896Z (almost 2 years ago)
• Topics: apache-kafka, docker-compose, elastic-apm, github-actions, kubernetes, nodejs, react, redis, sonarqube, test
• Language: JavaScript
• Homepage:
• Size: 287 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Backend Appvideos

-  Backend: [backend-appvideos](https://github.com/felippedesouza/backend-appvideos)

-  Frontend: [frontend-appvideos](https://github.com/felippedesouza/frontend-appvideos)

-  Backend que implementa o consumer no kafka: [backend-kafka](https://github.com/felippedesouza/backend-kafka)

## Clonando os diretórios

Rode o script

```bash

mkdir appvideos \

 && cd appvideos \

 && git clone https://github.com/felippedesouza/frontend-appvideos.git \

 && git clone https://github.com/felippedesouza/backend-appvideos.git \

 && git clone https://github.com/felippedesouza/backend-kafka.git

```

## Usando Docker Composer

O docker compose usa uma rede externa já criada, ao invés de ele criar, então é preciso criar uma rede. O mesmo serve pro volume do mysql.

-  `docker create network --diver bridge appvideos`

-  `docker volume create --name=v_mysql`

**Espere terminar a criação dos containers de cada arquivo para executar os outros arquivos**

Ordem de execução:

1. `docker-compose -f ./backend-appvideos/containers/kafka/docker-compose.yaml up -d`

1. `docker-compose -f ./backend-appvideos/containers/elastic/docker-compose.yaml up -d`

1. `docker-compose -f ./backend-appvideos/docker-compose.yaml up -d`

   1. `docker-compose exec backend-appvideos npx sequelize db:seed:all`

   1. `docker-compose exec backend-appvideos npm start`

1. `docker-compose -f ./backend-kafka/docker-compose.yaml up -d`

1. `docker-compose -f ./fronted-appvideos/docker-compose.yaml up -d`

   1. `docker-compose exec frontend-appvideos npm start`

## Usando Kubernetes

- `kubectl apply -f ./backend-appvideos/k8s/1_mysql.yaml`

- `kubectl apply -f ./backend-appvideos/k8s/2_redis.yaml`

- `kubectl apply -f ./backend-appvideos/k8s/3_backend.yaml`

- `kubectl apply -f ./frontned-appvideos/k8s/frontend.yaml`

## Comandos usados

### Docker Compose

- `docker-compose -f compose-api.yaml up`

- `docker-compose -f compose-api.yaml down`

- `docker-compose -f compose-api.yaml logs -f backend-appvideos`

- `docker-compose -f compose-db.yaml up -d`

- `docker-compose -f compose-db.yaml down`

- `docker-compose -f compose-db.yaml logs -f mysql`

- `docker-compose -f compose-db.yaml logs -f phpmyadmin`

### Kubernetes

mysql e redis, espere o container ser criado pra depois cria o backend

- `kubectl port-forward svc/backend 3001:3001`

- `kubectl port-forward svc/frontend 3000:3000`

- `kubectl apply -f configmap.yaml`

- `kubectl apply -f app.yaml`

- `kubectl get po (ou 'pods')`

- `kubectl get svc (ou 'services')`

- `kubectl logs `

- `kubectl port-forward svc/ :`

- `kubectl port-forward svc/ 8000:80 (funciona pra loadbalancer ou padrao)`

- `kubectl describe deployment appvideos`

### Explicando a rede no K8S

1. MySQL e Redis só serão usados dentro do cluster k8s, então o service é do tipo ClusterIP

1. O frontend precisa ter acesso externo ao cluster, por isso seu tipo é LoadBalancer.

1. O backend poderia ser do tipo ClusterIP, já que seu acesso seria so dentro do cluster, porem o frontend está sendo acessado fora do cluster (Browser) e quando haver uma requisição do tipo GET, ele precisa ter acesso ao cluster pra acessar o backend. Logo seu service é tipo LoadBalancer.