Celery vs Channel

 

Celery
channel
Celery is an asynchronous task queue/job queue based on distributed message passing.
It does this by taking the core of Django and adding a fully asynchronous layer underneath, running Django itself in a synchronous mode but handling connections and sockets asynchronously, and giving you the choice to write in either style.
https://en.wikipedia.org/wiki/Asynchronous_Layered_Coding
Django Channels is detailed as "It extends Django's abilities beyond HTTP - to handle WebSockets, chat protocols, IoT protocols".
not use protocol
Celery can be classified as a tool in the "Message Queue" category
Django Channels is grouped under "Frameworks (Full Stack)".


both open source
both open source

Comments

Post a Comment

Popular posts from this blog

Django Rest Framework Many To Many Relation with intermediate Table Serialization Example

Here, MLmodel and prediction models have not relationship class PredictionSerializer(serializers.ModelSerializer): prediction_result = PredictionResultSerializer(many=True, read_only=True) prediction_algorithms = serializers.SerializerMethodField() class Meta: model = Prediction fields = '__all__' def get_prediction_algorithms(self, mlmodel_instance): predmodel_query = PredModel.objects.filter(prediction=mlmodel_instance) pred_model_list = [ModelPredSerializer( model).data for model in predmodel_query] mlmodel = [] for ml in pred_model_list: alg = MlModel.objects.get(id=ml['model']) algo_dic = {"id": alg.id, "model_short_name": alg.model_short_name, "model_name": alg.model_name, "model_type": alg.model_type} mlmodel.append(algo_dic) return mlmodel Django Rest Framework Many To Many Inter...
Read more