simple-microservice

🏦 Go Microservice: Banking Simplicity

• Welcome to the no-nonsense zone! This Go program means business, simulating a banking application using the Back-End-to-Frontend (BFF) pattern. It's like the efficient, no-frills cousin of banking microservices.

🛠️ What's Inside?

• Cut to the chase: this microservice handles fund transfers between predefined bank accounts. Simple, straightforward, and no gimmicks.

🔧 Tech Essentials:

• Powered by Go Lang and wrapped in a Docker image, it's the real deal. The Back-End-to-Frontend (BFF) design pattern keeps things neat and tidy. No magic tricks, just solid coding.

🌐 Where's the Action?

• Catch the action on port 8081 via HTTP server. Need access? Head straight to the /auth route. No velvet ropes, just straightforward functionality.

⚙️ Ready to Roll?

• Think of this Docker image as your trusty tool. It gets the job done without unnecessary frills. Efficient, effective, and ready to roll.

• No flashy lights, no confetti, just a reliable banking microservice doing its thing. Let's get down to business!

📸 Screenshot:

Check out this sneak peek into the action:

• v1.1.0 (stable)

🐳 Docker Image

You can find the Docker image for the frontend on Docker Hub. To pull the image, use the following command:

docker pull luisvinhali/web-banking-frontend:latest

This will expose the frontend on http://<ENDPOINT>:8080/auth.

🐳 Docker Image

You can find the Docker image for the backend on Docker Hub. To pull the image, use the following command:

docker pull luisvinhali/web-banking-backend:latest

This will expose the backend on http://<ENDPOINT>:8081/transfer and http://<ENDPOINT>:8081/output.

By default, the frontend is configured to communicate with the backend at http://<ENDPOINT>:8081/transfer. Ensure that the backend container is running and accessible for seamless integration.

Feel free to explore and customize the code according to your requirements. For additional details, refer to the documentation in the respective GitHub repositories:

• Frontend Repository: luisvinhali/web-banking-frontend
• Backend Repository: luisvinhali/web-banking-backend

Using Docker Run:

Frontend:

docker run -p 8080:8080 web-banking-frontend:1.0

Backend:

docker run -p 8081:8081 web-banking-backend:1.0

Using Kubernetes:

Apply the following YAML manifest:

kubectl apply -f deploy.yaml

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-banking-frontend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-banking-frontend
  template:
    metadata:
      labels:
        app: web-banking-frontend
    spec:
      containers:
      - name: web-banking-frontend
        image: web-banking-frontend:1.0
        ports:
        - containerPort: 8080
---
apiVersion: v1
kind: Service
metadata:
  name: web-banking-frontend-service
spec:
  selector:
    app: web-banking-frontend
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080
  type: NodePort
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-banking-backend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-banking-backend
  template:
    metadata:
      labels:
        app: web-banking-backend
    spec:
      containers:
      - name: web-banking-backend
        image: web-banking-backend:1.0
        ports:
        - containerPort: 8081
---
apiVersion: v1
kind: Service
metadata:
  name: web-banking-backend-service
spec:
  selector:
    app: web-banking-backend
  ports:
    - protocol: TCP
      port: 8081
      targetPort: 8081
  type: NodePort

Here is a concise technical overview of the sections of the code:

Backend

Frontend

Common

Prometheus

Jaeger (service name is digital-bank in version 1.0.0)

Workflow