How do you tackle such problems?

It will be helpful if Kafka can come up with a pluggable system for storing configurations instead of Zookeeper. In that case problems such as the one you faced could be solved.

This is really helpful. I might even use this in my next product.

One question though, I don't see a 'type' field in Notification class. Won't it be helpful if notification type can be saved to identify if the notification was an email notification or push notification and so on?

Thanks! In this last version, we decided to move all notions of channels (sms, push, etc.) to the classes. So each notification has a `trigger_name` linking it to the class form the @message decorator. So you can identify notifications that way, but you can't infer the channels they'll use.

Got it now! But why was there a need of message decorator? The same task could have been achieved using the Channel Class.

The @message decorator allows transmissions scheduling logic not to have to be extended by your own code to focus on the actual Channel and Message logic. This way, the code is also magically indexing all the transmissions notification classes for when they need to be loaded asynchronously in the worker.

And if you meant that transmissions could have forced a couple of channel tasks, we would have missed the content of notification, the logic to check for validity, etc.

Indian software industry has changed drastically in past 5 years. People are building good software products in India specially people just coming out of colleges. But the biggest problem that I have seen is that people generally don't get good beta testers who are interested in improving the product. And it's not just about beta testers, users of an enterprise saas are also limited.

In such a scenario there is a disconnect between the creator and users. Only if NotCrud can get both these communities together, I think it can gain much attention. And not just attention it will be able to create a credible platform, just like HN and not HackerStreet, which will be used by both Users and Creators. Because showing off is not enough. In the end you want to improve your product.

Btw notCrud is a very good initiative. I am glad you are taking it.

I like the indentation part of PEP 8. Especially the ways to organise arguments while defining functions. Having a common way of writing those is really helpful when reading the code. https://www.python.org/dev/peps/pep-0008/#indentation

This is really incredible list. Very useful when in need. Especially the switches that come in very handy.