Skip to content

Comment on Ask HN: Best Python web frameworkparent

Comments

Disagree, Django Rest Framework and TastyPie make REST APIs effortless: write Django models, register them with the REST plugin, hook the plugin to your main URL structure. They're a really good example of how Django enables reuse.

Implementation-wise they both hook into the model framework and the form framework, although you can swap out those parts if your data lives elsewhere.

I see what you're saying.

But I disagree that:

Database = Model = Resource

There's flexibility. I've gotten a lot of mileage of closely-related models inlined into a parent model to form a single resource (resource relationships annotated with full=True with TastyPie), but one isn't limited to that either; http://django-tastypie.rtfd.org/ outlines the possibilities better than a short comment could.

The parent comment was only pointing out how incredibly fast and easy it is to get started with TastyPie. The moment you decide to create an API resource that isn't a one-to-one mapping with a database table or Model, TastyPie is still able to come with you every step of the way.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.