Skip to main content

The 10 Python Conferences Happening at PyCon 2011 (part 3)

This is the third in a series of posts about the schedule for PyCon 2011. In designing this schedule, we found that there are actually 10 different conferences happening in parallel at PyCon. The first post introduced the series and discussed the Django virtual track. The second post focused on the web working virtual track. This post focuses on the third virtual track, Python and NoSQL.

Python and NoSQL

One of the more interesting developments in the past couple years is the use of NoSQL databases. FOr many years, the default answer to any kind of persistence problem was simply to put it in a (relational) database. If you had problems scaling, then you would shard or pay lots of money for clustered/big iron solutions. NoSQL developed in part as a reaction to the overuse of RDBMSes for all sorts of problems.

Of course, it can be hard to say exactly what NoSQL is - but I like to define it as a resurgence of "the right tool for the job," just applied to the storage and persistence space. It can be graph-based, document-based, column-based, or object based -- or even just a data structures server.

It is not surprising, though, that Python is able to talk to them all. In this track we have four different talks, giving the inside scoop on production-level use of various NoSQL stores.

ZODB: A Python Persistence System by Chris McDonough. The ZODB is the granddaddy of the various NoSQL options for Python, having been developed when such things were "object databases" and not "NoSQL." Nevertheless, the ZODB is a standalone persistence system uniquely integrated into Python that remains astoundingly buzzword-compliant despite its age. This talk will provide a high-level overview of ZODB useful to a novice or intermediate Python programmer. At the end of the talk, an attendee should have a basic understanding of how to create an application which depends on ZODB persistence.

CouchDB and Python in practice by Luke Gotszling. CouchDB has a unique document-centric model with automatic clustering and replication. It is gaining a lot of traction, and has recently been seen both up in the clouds and as a data store on Android phones. This talk will introduce CouchDB and will show how to get it to play well with Python. Luke will continue by showing a python ORM for CouchDB, easing development and object-document interoperability. Finally, Luke will cover parsing CouchDB documents within python, writing view functions in python, map/reduce functions on CouchDB from python, and some lessons learned from managing and distributing a live deployment at scale under high load.

Scaling Python past 100 by Mark Ramm. Those with eagle eyes will spot this as a repeat from the "web working" track. That is because this talk is a twofer - describing both the development of the modern Python codebase as well as the use of MongoDB to address the scaling issues associated with a top 100 site.

MongoDB + Pylons at Catch.com: Scalable Web Apps with Python and NoSQL by Niall O'Higgins. The Catch.com backend provides an API for publishing and querying your personal data - used by many hugely popular Android, iOS and Web clients. Faced with the limits of the initial Catch.com Java/BDB backend implemention, they evaluated various alternative technologies including Amazon SimpleDB, MySQL, Cassandra and MongoDB. They found Python and MongoDB gave them unique flexibility with our data model, allowed them to scale for increased reliability and performance and decreased feature development time - and in this talk they'll describe exactly how.

Edit: Wesley Chun points out that Running Django Apps on Google App Engine is also designed to deal with NoSQL datastores - and that the principles covered in his talk apply both to GAE and to MongoDB. ed.

Is this the conference you want to see? Then, register for PyCon and book your room now! We have picked up a few more rooms - including a few at a lower rate a block away. You can email (pycon4-reg@cteusa.com), or phone (847-759-4277). We have very few spots left.

Links:

Edit: Discussion link on Hacker News.

Comments

Popular posts from this blog

PyCon 2018 Code of Conduct Transparency Report

The PyCon Code of Conduct sets standards for how our community interacts with others during the conference. For 2018 the Code of Conduct underwent an extensive overhaul, our procedures for reporting and responding to incidents were improved, and our on-site methods were improved. You can read more about the updates for 2018 here. Cumulatively these changes were meant to improve the safety, welcoming nature, and overall inclusivity of PyCon. Based on initial responses, feedback, and incidents reported this year we feel that we made progress on those goals. A Code of Conduct without appropriate reporting and response procedures is difficult to enforce transparently, and furthermore a lack of transparency in the outcomes of Code of Conduct incidents leaves the community without knowledge of how or if the organizers worked to resolve incidents. With that in mind, we have prepared the following to help the community understand what kind of incidents we received reports about and how the PyCon…

PyCon 2018 Registration is Now Open!

We’re thrilled to announce the opening of registration for PyCon 2018 in Cleveland, Ohio! The prior six PyCons have sold out, so prepare for another one and get your tickets early. The first 800 tickets sold are priced at an early bird discount, saving over 20% on corporate tickets and over 12% on individual tickets. Students save $25 if they purchase early!

To get started, create an account and head to https://us.pycon.org/2018/registration/ to get your tickets!

You get a package that is hard to beat when you register for PyCon. The conference itself is three days worth of our community’s 95 best talks, amazing keynote speakers each morning, and our famed lightning talks to close out each day, but it’s much more than that. It’s having over 3,000 people in one place to learn from and share with. It’s joining a conversation in the hallway with the creators of open source projects. It’s taking yourself from beginner to intermediate, or intermediate to advanced. For some, it’s getting st…

How to get ready for the PyCon development sprints

[A guest post by Kushal Das, one of the 2016 Sprint Coordinators]So — you have already decided to join in the PyCon development sprints! The sprints run for four days, from Thursday to Sunday after the conference. You do not have to be registered for the conference to attend the sprints! Some teams plan to write code over all four days, while some projects plan a shorter sprint if the organizers cannot stay for all four days.Can you start getting prepared for the sprint ahead of time? Yes!There are several things you can do ahead of time, that can save effort once you arrive at the sprints — and some preparations can even be made at home, before you arrive at PyCon:Have your operating system updated and patched — whether Mac, Windows, or Linux. This eliminates one possible source of problems with getting software up and running.Go ahead and install the version control system that will be used by the projects you are interested in. If you install both git and Mercurial on your computer…