Lightweight Django (2014) [0] actually explores using the Django framework in a similar manner.

[0] https://www.oreilly.com/library/view/lightweight-django/9781...

I think one common misconception is that Django can't be used in place of Flask when you want a minimalist set up. And to be fair, I used to think the same until I read Lightweight Django [0]. Their smallest django project code is just a couple of lines:

    import sys     from django.conf import settings      settings.configure(         DEBUG=True,         SECRET_KEY='thisisthesecretkey',         ROOT_URLCONF=__name__,         MIDDLEWARE_CLASSES=(             'django.middleware.common.CommonMiddleware',             'django.middleware.csrf.CsrfViewMiddleware',             'django.middleware.clickjacking.XFrameOptionsMiddleware',             ),         )              from django.conf.urls import url     from django.http import HttpResponse       def index(request):         return HttpResponse('Hello World')               urlpatterns = (         url(r'^$', index),     )      if __name__ == "__main__":         from django.core.management import execute_from_command_line          execute_from_command_line(sys.argv)  

Granted, it's not as terse as Flask's hello world example but it's still quite short.

[0] https://www.oreilly.com/library/view/lightweight-django/9781...

Have you looked at: http://www.django-rest-framework.org/

and the Lightweight Django book: http://shop.oreilly.com/product/0636920032502.do

If you plan to use Django as an API server, you might be interested in Lightweight Django (http://shop.oreilly.com/product/0636920032502.do), which shows you how to design and build an API server using Django, Django Rest Framework (another great Django related project) and Backbone on the front-end.

You might take a look at Lightweight Django: http://shop.oreilly.com/product/0636920032502.do

I don't get it: why does moving to microservices mean ditching Django? Couldn't you take your Django monolith and break it into separate (still-Django) microservices? I get that Django is seen as "too heavyweight" to do such a thing, though there are literally books (http://shop.oreilly.com/product/0636920032502.do) written about how to slim down Django.

I get that monolith to microservice is all the rage these days, I just don't understand (and the article doesn't really say) why you have to "ditch Django" to do that.