Microservice with django

[salimon jamiu olashile]

Hello all,

How can I build a Django project/app that follow the microservice architecture?

Looking to be pointed in the right direction.

Best regards.

[Salim Kachemela]

I was wondering the same thing

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFhdOCNZ%2BR084HQc1FD5a%2BT%3D_umuH87haQbe%3DyD2aAT6SKtUsg%40mail.gmail.com.

[Murilo A. Gigliotti]

All,

Good question! I would like more details... Thank you!

 

Rgds,

_____________________________

Murilo Gigliotti,

Odoo Business Partner

Mais informações visite http://www.gigliottitech.com.br/

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CACB6%2B1-9tNHnZ8X7U_EwqQx6%2B_msMhThvOif2RBuEuNbY3QVXQ%40mail.gmail.com.

[Ing.Daniel Bojorge]

Me too!!!

Dios L@s Bendiga

Saludos,

daniel.bojorge about.me/daniel.bojorge

Curso Desarrollo Web con Python usando Django 2.2 Para Principiantes con Descuento 95%   

WebService RestFul API con Python usando Django RestFrameWork

Fácil Replicación de Cualquier Base de Datos y/o Sistema Operativo

Programación en Capas (Web y Escritorio)

Mi Blog

Nicaragua

"Si ustedes permanecen unidos a mí, y si permanecen fieles a mis enseñanzas, pidan lo que quieran y se les dará.
(Juan 15:7 DHH)
Bendito el varón que se fía en el SEÑOR, y cuya confianza es el SEÑOR.
(Jeremías 17:7 RV2000)

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/055701d59661%24ed290420%24c77b0c60%24%40com.br.

[Nick Sarbicki]

There is not really anything that requires doing to make Django work with microservices or as a microservice.

It is completely agnostic to your overall architecture.

Just simply create a new django project for each microservice you want to create. There honestly is nothing else to it.

- Nick

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMQeQjZ%3DWtKWS0nTxsFgyGJ6BFwHJUDYbz6BLFH_rnieTn_XRQ%40mail.gmail.com.

[salimon jamiu olashile]

I’ve a group project to work on. It’s a bug tracking system & we decided to go with a microservice architecture which is the best solution for the assumed business scenario. I am to build the Reporting functionality as a seperate service.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/055701d59661%24ed290420%24c77b0c60%24%40com.br.

[Shaheed Haque]

At the end of the day, assuming you combine the Django "application server" with a REST wrapper, you can build any level or type of service you could want.

The crucial question is how you want to trade off the power of the ORM against custom code? For example, let's say you wrapped every single table (Django model) in a separate "nano"service... Then you could not use sql to Jon or select anything and everything would be custom code.

OTOH, if you put everything in a single service, you can freely use the ORM but loose whatever advantage you hope to fain from the modularity of soa. 

Hth, Shaheed

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFhdOCP8rGBzBoiYqQ_CtaQdNEN%2BKM5NqhBKBcAe0C9%2BP-ZKaw%40mail.gmail.com.

[Uzama Zaid Mohammed Jaward]

1. If your application going for production, then don’t start with Microservices. Microservices used to scale up your application in horizontally as well as there are other some benefits like each service can build with small amount of team, therefore maintaining and testing is pretty easy. If you write your application in Microservices you should have strong Devops to maintain.

 So start with monolithic and later you can change to microservices when you need to scale your application. 

2. If you just need to use micro service architecture in your college projects then you can use docket for running each services. You can exchange data between services using REST APIs. Also you can use Kubernetes for docker container management. Also you use message brokers to communicate between services where one can publish and others can subscribe. For the message broker try Apache Kafka. 

This is my suggestion. There are plenty of blog post available on the internet 

  

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHAc2jfkY1%2BzGbWBCHm3_pP4J3fzwg_wirrqDPQM%3DQ1f7OXWAw%40mail.gmail.com.

[Integr@te System]

Hi Freinds,

start rightnow by use djangorestframework

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAOHA2_2m6V9LRKsCDc8eWX6j1bgE%2BN_ZdJ7HwJAztnsMJNWmFQ%40mail.gmail.com.

[Parth Joshi]

Agree with Nick.

It's an approach problem. Not a framework problem. Unless framework does not support Service Layering. But its not likely for Django, as it can support such architecture. 

Referring DDD and Onion Architecture might help (DDD is for Statically typed languages like Java etc, but there are people building patterns around it (Github: Python Leap Book, etc) using Python).

Its all about segregation, decoupling and separation of concerns at service level rather than code level (Putting in plain and simple terms). So it's all about researching and adopting a right pattern.

 

Regards, 

Parth Joshi

<image001.png> Odoo Business Partner

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAGuvt93KeEBDvO_4sy123SoEsmcRr973tZt%3DxmZUv9NgnVTqGw%40mail.gmail.com.