Summary

Are you looking for a backend as a service offering where you have full control of your data? Look no further than Kinto! This week Alexis Metaireau and Mathieu Leplatre share the story of how Kinto was created, how it works under the covers, and some of the ways that it is being used at Mozilla and around the web.

Brief Introduction

• Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
• I would like to thank everyone who has donated to the show. Your contributions help us make the show sustainable.
• When you’re ready to launch your next project you’ll need somewhere to deploy it. Check out Linode at linode.com/podcastinit and get a $20 credit to try out their fast and reliable Linux virtual servers for running your awesome app.
• You’ll want to make sure that your users don’t have to put up with bugs, so you should use Rollbar for tracking and aggregating your application errors to find and fix the bugs in your application before your users notice they exist. Use the link rollbar.com/podcastinit to get 90 days and 300,000 errors for free on their bootstrap plan.
• Visit our site to subscribe to our show, sign up for our newsletter, read the show notes, and get in touch.
• To help other people find the show you can leave a review on iTunes, or Google Play Music, and tell your friends and co-workers
• Join our community! Visit discourse.pythonpodcast.com for your opportunity to find out about upcoming guests, suggest questions, and propose show ideas.
• Your host as usual is Tobias Macey and today I’m interviewing Alexis Metaireau and Mathieu Leplatre about Kinto

Interview with Alexis and Mathieu

• Introductions
• How did you get introduced to Python?
• What is Kinto and how did it get started?
• What does the internal architecture of Kinto look like?
• Given that the primary data format being stored is JSON, why did you choose PostGreSQL as your storage backend instead of a NoSQL document database such as CouchDB?
• Synchronization of transactions from multiple users, including offline first support, is a difficult problem. How have you approached that in Kinto and what are some of the alternate solutions that were considered?
• Designing usable APIs is a complicated subject. What features did you prioritize while creating the interfaces to Kinto?
• What are some of the most innovative uses of Kinto that you have seen?
• What are some of the biggest challenges that you have faced while building Kinto?
• What do you have planned for the future of Kinto?

Keep In Touch

• Kinto
  • Github
  • Mailing List


• Alexis
  • Email


• Mathieu
  • Twitter
  • Email

Picks

• Tobias
  • What are you working on this week with Python?


• Alexis
  • Miles Davis – Bitches Brew


• Mathieu
  • Sigal
  • Subliminal

Links

• Pocket
• CouchDB
• OpenAPI
• WebCrypto
• Formbuilder
• Firebase
• Kinto Comparison Table
• Mozilla Persona
• Portier

The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA