Building Big Applications in Python

Jeff Rush (~jeff)


4

Votes

Description:

Learn about the common elements of building big applications, which architecture variables have to be balanced, why they matter and how to achieve that.

This talk comes from our use of Python to build a web application product over the last 15-years at ZeOmega, a healthcare software company based in Bangalore. But the talk is domain-generic and offers solutions above the code level, at the architectural level

  • seek balance between your I/O and CPU
  • distribute your message processing
  • reduce complexity in your request authentication
  • objectify your persistent data
  • design for introspection

I close with a brief summary of how we have leveraged these to build a flexible set of features into our product.

Prerequisites:

No prerequisites as this is a high-level talk about architecture design.

While some of the software mentioned will be new to some attendees, I will carefully explain what it is and how it is useful. I will avoid buzzwords and acronyms.

Content URLs:

Draft Copy of My Slides on SlideShare for your review. I will keep updating them as I work on them.

Speaker Info:

Jeff has been involved with Python since version 1.5.2, years ago. He ported it to OS/2 (remember OS/2 anyone?) and in the past, been Python Advocacy Coordinator, organizer of the Dallas/Ft. Worth Pythoneers usergroup as well as conference co-chair of PyCon 2006/2007,

These days he is chief technology officer of ZeOmega, a provider based in Bangalore of healthcare software written in Python for the U.S. healthcare payer/provider enterprise market.

Jeff is travelling from Dallas, Texas in the U.S. to fulfill one of his dreams to attend PyCon India. You can also find him sometimes at the ZeOmega offices in Bangalore. His favorite food is Murgh Makhani and a Mango Lassi, finished off with Gulab jamun or Gajar Halwa!

Section: Concurrency
Type: Talks
Target Audience: Intermediate
Last Updated:

I have received your comments that more details are needed and I am working up a draft outline/slide set to convey that.

Jeff Rush (~jeff)

After considering your comments, I have renamed the talk to be more generic, created an initial set of slides that I've shared with you, and shifted the focus to the "why" of architectural decisions. In the talk I'll discuss the use of Pika/RabbitMQ, Pyramid/Zope, ZSQL, SQLAlchemy, RESTful principles, Python decorators, AngularJs and websockets over the STOMP protocol.

I will keep the mention of healthcare to a minimum, to make the talk useful to anyone building a 500-1000 user all-day business-class web application.

Jeff Rush (~jeff)
The comment is marked as spam.

MarkThomas

Login to add a new comment.