The coffee shop

This is a small demo of a coffee shop application for practicing Golang code and technologies. In this project, I aim to separate it into microservices and design features using various technologies.

1. How to run

    1. `cd deployments/` open cmd: `docker-compose up`
    2. `cd ../` to root directory
    3. run counter-service `make run-counter`
    4. run kitchen-service `make run-kitchen`
    5. run product-service `make run-product`
    6. run authorization-service `make run-authorization`
    7. run batch-service `make run-batch`
    8. run html code in: ./web/ (cmd: `start index.html`)

User

Accounts and passwords is:
    - admin: admin
    - counter: counter
    - kitchen: kitchen

This is demo

2. Technical stack

    0. Docker + go verson 1.22.2
    1. routes - "github.com/gin-gonic/gin"
    2. gRPC - "google.golang.org/grpc" and protobuf
    3. redis - "github.com/go-redis/redis/v8"
    4. cron job - "github.com/go-co-op/gocron/v2"
    5. kafka - "github.com/IBM/sarama"
    6. minio - "github.com/minio/minio-go"
    7. gorp_migration - "github.com/rubenv/sql-migrate"
    8. goqu - "github.com/doug-martin/goqu/v9"
    9. google wire - "github.com/google/wire"
    10. ratelimit - "golang.org/x/time/rate"
    11. bycrypt - "golang.org/x/crypto/bcrypt"
    12. gofpdf - "github.com/jung-kurt/gofpdf"
    13. golangci-lint

3. Flow

Project structure

    1. authorization-service: for login/register authen, author
    2. counter-service: for receptionist to make order, find items and payment
    3. kitchen-service: kitchen process (in here I made it easily to view order and update finished order)
    4. product-service: manage all product of coffee store
    5. batch-service: to run end of day to make report (you can trigger it by manual)
    6. FE: html code to demostration how does APIs work?

Sequence diagram

4. How's it work

Please import coffee-project.postman_collection.json to your postman and run it

5. Authorization

When you call login the API will response 2 token:

• token (main token)
• refreshToken (token with longer expired time. It can help renew token when the main token is expired)

I you meet httpCode = 407 please call API /api/v1/renewToken

{
    "code": 200,
    "message": {
        "refreshToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MTczMDMzMDksInJvbGVzIjpbIm1lbWJlciJdLCJ1c2VySWQiOiJuYW1udiJ9.PX7DvULwCDwYsy_0UdUx21AXLBS4WV-x--E1wFv-LtI",
        "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MTcyOTYzMzksImlhdCI6MTcxNzI5NjMwOSwicm9sZXMiOlsibWVtYmVyIl0sInVzZXJJZCI6Im5hbW52In0.TEH-1oX5PrXpCNBWf4EoPVpCGVAkb1DVezzMtYEC8fU"
    },
    "status": "OK"
}

├───api
│   └───grpcpb
│       ├───gen
│       └───swagger
├───cmd
│   ├───authorization
│   ├───batch
│   ├───counter
│   ├───kitchen
│   └───product
├───config
├───deployments
├───docs
├───internal
│   ├───authorization
│   │   ├───app
│   │   ├───domain
│   │   ├───repo
│   │   └───service
│   ├───batch
│   │   ├───app
│   │   ├───domain
│   │   ├───handler
│   │   │   └───jobs
│   │   ├───repo
│   │   └───service
│   ├───counter
│   │   ├───app
│   │   ├───domain
│   │   ├───handler
│   │   │   └───router
│   │   ├───repo
│   │   └───service
│   ├───kitchen
│   │   ├───app
│   │   ├───handler
│   │   │   └───consumers
│   │   └───service
│   └───product
│       ├───app
│       ├───domain
│       ├───handler
│       │   └───router
│       ├───repo
│       └───service
├───pkg
│   ├───cache
│   ├───configs
│   ├───data_access
│   │   ├───enums
│   │   └───migrations
│   │       └───mysql
│   ├───mq
│   │   ├───consumer
│   │   └───producer
│   ├───ratelimit
│   ├───s3
│   ├───security
│   └───utils
└───web
    ├───css
    └───js