Python Microservices Full Course - Event-Driven Architecture with RabbitMQ

In this video, we will create a simple Microservices example with Python Django and Python Flask, We learn how to create an Event-Driven Architecture with RabbitMQ. The apps will use Python Pika to send events to the other apps and everything will seem to work as a Monolithic app but is actually a Microservices app.

00:00:00 Introduction
00:04:05 Django Setup with Docker
00:11:08 Database and Migrations
00:20:17 Django Products CRUD
00:36:29 Flask Setup with Docker
00:50:21 RabbitMQ
00:58:01 Consumer Service
01:02:55 Data Consistency
01:10:37 Finishing the apps

#python #microservices #django #flask

[astrolillo]

Excellent, no fluff, no idiotic remarks, no yelling, very refreshing, compared to most coding youtube "teachers"

[cbaxtermusic]

Great Application, Very easy to follow, and an awesome example of using multiple technologies for a project.

[henriquekubenda]

pretty straightforward, it was even fun to follow, thanks a lot!

[saifgaida]

before even starting you know it's gonna be awsome!! thank you for sharing

[Rajx]

Basically 9:35 volumes of docker-compose work like synced directory with container and host application folder.

[natetolbert]

What is the point of creating a virtual environment inside a docker container? Seems a bit redundant...

[brucehaskinvt]

Quality work. Greatly appreciate your efforts.

[wispawelwis]

this is how you make tutorials, thanks

[futhedude]

recap:
this video is about 2 module: "product" and "main"
"main" is like a client side where it will list the products and client can give it a "like", this service is by django
"product" is like a admin side where admin can do CRUD for the products, this service is by flask
the database is basically the same, except for the "like" behavior.

this 2 service use rabbitMQ to sync data to each other.
Ex: when admin do CRUD for the products in the "product" service, it will create message to sync to the "main" service as well.
when client give product a "like", it will create message to sync to the "product" service as well.

[kamaleshpramanik]

This is an awesome video. Thank you very much Sir.

[ashokavanjare]

Thanks for your videos. Excellent Explaination.

[vineethsai]

If anyone gets `OSError: mysql_config not found` when installing mysqlclient, Make sure to install this first
`sudo apt-get install libmysqlclient-dev` For Linux users.

[brucebatmanwayne]

is it difficult to answer "why" before just copy pasting the code? eg: at 27:53, couldn't you have mentioned why you are copy pasting the code? it's a "python microservice course" not a Django course. It is bad teaching habit in my opinion to assume the learner would be familiar with Django

[HARSHYADAV-wkzb]

can the frontend directly interact with the rabbitmq. consider a scenario where there may be lot of api calls that might slow down the server so can we directly update the queue from frontend

[davitkvaratskhelia]

Happy 3 years anniversary to this video!

[juanandresrodriguezpedreir]

I´m unable to connect to the database at 14:44. Do I need any docker image configuration not mentioned?

[TheAremoh]

Thanks for this tutorial.
My question is, can I also create the consumer file in the product app of the admin?

[cando_jo]

why did you have to copy requirements.txt first in the Dockerfile? Aren't you copying everything anyways?

[snagendra]

good work, thanks for posting in youtube .as you said in description it seems monolythic but is not. can you/anyone say at where it is representing microservices.

[chihabahmed]

Hi there,

Do you think its a good idea to have auth service, account service in a microservices or just one of them responsible for login, logout, register, delete account, forgot password etc etc

at the moment I have two service, auth and account

account is responsible for adding user and other user profile features.
the auth is only responsible for issuing token when the user tries to request. so it only has one function at the moment

but thinking about this, I realized that I am over doing things, I could include anything to do with user in one service and thats it instead of having account service talking to auth service about a new user added.

do you get my point ?

what is your input on this ?

do you think its a good idea to have auth service and account service or the account service alone should be enough and later I can create a service that will responsible for controlling users settings as an example.

so basically what I mean, I should have one service called "account service" and that service is responsible for adding user, login, logout etc etc just like in a monlith app or two services, one responsible for generating token and checking if users is banned, not verified.

so for example, if I ban a user, I only need to switch that isBanned to true from the auth.

well I could do the same in account service.

what do you think a good option to have or both are valid
thanks