An amazing list of do and don't. Written by folks at vinta software who have been building reusable django apps for a while.
Compose Enterprise with dedicated servers, encryption, premium support and more.
Lately, one that’s been on my mind a bit is testing. I’m a fan of testing, and on my personal apps I have CI set up to run on every pull request and every commit I push, against the full combinatorial matrix of Django/Python versions I support. I also use coverage.py, and have it set to break my builds if I ever go below 100% test coverage. So far, so good. And, of course, Django itself supplies a bunch of built-in tools to make testing easier and nicer. But I still feel like good patterns for testing are an area where Django could do a lot better. So let’s dig into some of the pain points.
I frequently face a recurring situation when developers receive a task to make a performance optimization on Django. Pretty often they are trying to make it in a wrong way. In this short article I want to shed some light on the common mistakes, and show you the way I'm searching for bottlenecks.
Django Admin is a powerful tool for managing data in your app. However, it was not designed with summary tables and charts in mind. Luckily, the developers of Django Admin made it easy for us to customize.
Back in university I never enjoyed writing SQL. It was only at my last employer ( Intellus Learning now acquired by Macmillan ) I had to read and write quite a lot of SQL queries, some of them fairly complex. So now rather then use ORM I tend to just write the SQL queries and be done with it. I don't consider myself good at SQL as a matter of fact it would take me some time to figure what the 50 line SQL query is doing. Now with that perspective I can say that if you only know ORM and no clue what's happening underneath it may get to you one day in terms of performance issues and not knowing that your ORM is resulting in multiple SQL queries spanning tables.
Django app for sending emails, handling scheduled email jobs, managing email subscriptions, email analytics, etc.
A Django email backend that uses Boto3 to interact with Amazon Simple Email Service (SES).