Just for a bit of perspective... My SqlAlchemy integration for a project is connected to two distinct applications :
- Pyramid -- Web Application - Celery -- Background Processing We're also hoping to get it working on a third - Twisted -- More Background Work There are a lot of moving parts here. All the libraries (even the twisted) , reference a core library for our Project. If we hadn't decided to be as barebones as possible in our SqlAlchemy model, even the celery integration would be a huge pain. Our models only deal with mapping the database / relationships and being able to serialize/validate themselves. The business logic usually happens within each service , but when there is something that is useful / needed across services, we migrate into the shared library and it becomes an "internal api" function. That approach has let us be relatively fast ( though not as fast as if we just jammed stuff into the model ), while keeping everything scalable. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
