diptochakrabarty / api-gateway-kong-golang

API Gateway developed using kong , golang and python services for a authentication and operations service where golang service acts as authentication mechanism and python service is backend and kong is gateway

Hello There 👋

• I am Dipto Chakrabarty 😊 . I am working as a SRE at @CISCO

• I am a Devops and Python enthusiast 🧰

• I have done multiple projects ranging from the field of Devops , Backend to Cloud Computing and Automation 🗄️ .

• I am currently brushing up my skills and plan to learn Golang and Terraform .

• I am willing to work on free-lance projects and love to contribute to open source projects 💡

• 🧲 You can checkout my projects from here 🔥 -

• Connect with me on LinkeDin 🎆 LinkeDin Profile 🎇

Tech Stack 💻

Programming Languages

Devops

Cloud

DataBases

Tools

My Certifications ⬇️

• Red Hat Certified System Administrator
• Red Hat Certified Specialist in Ansible Automation
• Red Hat Certified Engineer

My Activities 📬

BLOGS 📖	WEBINARS 📺
How Jenkins can help build your code	Micorservices with Docker
Kubernetes and Docker setup using Ansible	Guide to Linux
Automation with Ansible	Ansible Automation

If you like the Repository give it a ⭐ and also follow me on Github 😀 , you can also see my projects here Projects

api-gateway-kong-golang's Issues

Setup Docker Containers for each service

Currently we are using three services

• kong api gateway
• golang for authentication
• flask api for backend

It would be good to have the golang and flask api running inside docker containers and kong interacting with the containers instead of running them manually

Endpoint to register users in golang service

We do not have an endpoint to register new users , we are directly providing functionality to login users

It would be good to have a register endpoint which takes in users username/email and password and stores it in a database

Related to #17

Add a database to golang service to hold users data

Currently wt token and login endpoint only takes in a username and it is not stored anywhere.

It would be good if a database is present under which the authentication service can work on , users are stored in database and validated from the data present there.

So the flow would be

• user registers themselves in new endpoint
• their data is stored in database
• on logging in from login endpoint values are validated from database and jwt token is provided