Selected Talks for PyConf Hyderabad 2017 have been announced. Please Check the Confirmed Proposals section for the Selected Talks
Following are the guidelines for proposal submission
- Please mention type of Proposal as given below in the Title of the Proposal.
- The proposal should have an objective with clear expectation for the audience.
- The Proposal description should be short and to the point.
- The proposal should have proper prerequisites like environment setup, library version.
- No proposal will be selected without a link to appropriate session content like presentation, pdf, code snippets etc.
- Proposal content should adhere to code of conduct.
- Proposal content links can be updated later.
- Proposal content shouldn’t have a company name throughout the content. Mention of the employer is allowed only at the beginning of the content (presentation/pdf).
- Background image/wallpaper shouldn’t contain company name/logos.
- For any questions, please write to firstname.lastname@example.org.
We have three kind of Proposals - General Talks, Lightning Talks and Workshops. Please mention the Proposal type in the Title of the Proposal. Give a Title like Proposal Type : Proposal Title
These are the traditional talk sessions scheduled during the first day of conference. They will be conducted on Day 2 of Conference, Sunday, 8th Oct. The length of these tracks are 45 minutes.
These are short length talks that will be conducted on Day 2 of Conference, Sunday, 8th Oct. The time limit is 5 minutes. But we can extend it depending on number of talks submitted.
As with the talks, we are looking for Workshops that can grow this community at any level. We aim for Workshops that will advance Python, advance this community, and shape the future. Each session runs for 6 full hours plus a break for lunch. There will be 2 workshops going parallely on Day 1 of Conference, Saturday, 7th Oct in the same venue that hosts the main conference. Workshop I is aimed for Begineers while Workshop II is a Advaced Session aimed for Professionals.
These will be the themes and topics
- Core Python and Python 3 features
- Concurrent and Asynchronous programming in Python
- Data Science and Analysis
- Web Development
- Python and IOT
- Functional Programming
- Artificial Intelligence
- Continuous integration and Deployment
- Scientific Computing
- Cloud computing with Python
- 31st August, 2017 : Deadline for Proposal Submission
- 16th September, 2017 : Talk selection and announcement
IoT meets Serverless
Speed and agility are the most expected in today’s analytics tools. The quicker you get from idea to insights, the more you can innovate & perform ad-hoc data analysis. I will be talking about how we can use AWS serverless architecture to stream and analyze IoT data, managed by python. We can be up and running in minutes―starting small, but able to easily grow to millions of devices and billions of messages.
In this world of IoT, the hardware assembly of the tiny little sensors are just the tip of the iceberg. The real complexity lies in processing the massive amount of data these sensors generate. As I am typing this there are TeraBytes of data being generated every hour by connected things around the globe and the data is predicted to reach 403 ZetaBytes by 2018.
One cannot afford to spend most of the time on building and maintaining a backend servers to process this huge stream of data. The quicker you bring the data to the presentation tier, the more you can experiment and drive answers to new business questions. This is where we can leverage the agility of serverless architecture models. I will be talking about how AWS serverless architectures created and managed using python can help our case by taking care of the non-differentiated heavy lifting tasks such as managing servers, clusters, and device endpoints – allowing us to focus on assembling the IoT system, analyzing data, and building meaningful reports quickly and efficiently.
- The “thing” in “Internet of Things”
a. Quick introduction to IoT. How much and what data they will generate
- Let it in
a. Designing a data pipeline to handle the large stream of data
- Three-tier Architecture
a. Introduction to one of the common n-tier architecture approach
- Usual approach
a. How we traditianally implement a 3-tier architecture in cloud to handle data
b. Traditional architecture diagram (IoT gateway, kafka, storm, mongodb, cold storage)
c. Drawbacks in this approach
- Going serverless
b. Using AWS serverless for our 3-tier architecture
a. Brief explanation of all the services we use in AWS serverless
b. Services include AWS IoT, Kinesis Firehose, AWS lambda, S3, Athena, AWS Quicksight
- Up and running in minutes (demo)
a. Set up the serverless components on live using python and Boto3
b. Get quick insights from mock data or data from sensors (using already setup Arduino/Raspi)
An optimist by nature, Naren shows up late to meetings at MadStreetDen. In his 4 years of industry experience he’s worn plenty of hats- like the one of a Trainer, Embedded Engineer and Backend/Product Engineer and sometimes even helmets- when he’s out cycling. He is currently on a mission to help startups to design and write usable software even before making it reusable.
When he’s not stirring up code, you can find him whipping up a delicious gluten-free treat or travelling/cycling. He likes being asked about his endless love for Python through the handle @DudeWhoCode