JSFoo is in its ninth edition this year. Talks at JSFoo 2019 will cover the following topics:
- Component architecture -- how different web components have been stitched together to build apps; outcomes on UI and performance as a result of architecture choices
- Deployment practices for front-end and how Kubernetes and CI/CD fall into this picture
- Developer experience (DX)
- Functional programming paradigms: ReasonML and ClojureScript
- Privacy and Content Security Policy (CSP)
- New developments such as SvelteJS
Speakers from Razorpay, CloudCherry, Myntra, Innovaccer, GitLab, Microsoft, Atlassian and Gramener will share their work and learnings on these topics.
JSFoo is a conference for practitioners, by practitioners. JSFoo 2019 is a conference for:
- Front-end engineers
- Senior software developers
- Team leaders and engineering managers
- Fullstack developers
- InfoSec professionals
##JSFoo 2019 details:
Dates: 27 and 28 September
Venue: NIMHANS Convention Centre, Bangalore
The following workshops have been curated for before and after the conference:
For inquiries about conference tickets, workshop tickets and any other details, call JSFoo on 7676332020 or email firstname.lastname@example.org
For tickets and sponsorships, contact email@example.com or call +91-7676332020. For queries about proposing talks, write to firstname.lastname@example.org
What or how not to do in Redis world
What is Redis? Taking the first line on the website, “Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker”. You’ve been told how amazing Redis is and have seen many people present it as a silver bullet.
In this land of silver bullets, I would like to show you cases where Redis might fall flat on the face. Some things might be laughable and obvious, and I have seen some big teams make these mistakes, and some are going to be less obvious.
Bringing you my Redis failures and experiences.
What you can expect from this session:
- Some of the common mistakes and a few stories of people having burnt themselves
- (Mis) Using redis as a Persistent storage
- Single thread headaches
- Where redis screams & then some (Did someone say rate-limiting?)
Aram is a full stack developer who has worked on everything from Ruby, Python and NodeJS, to Html, CSS and Angular. He has used Redis in both places where it had to be used and places which he thought would be a good fit (and has successfully burnt himself). Aram has worked with startups writing the first line of code (including Cloudaria which was his own baby) and consulted for some of the more notable Forbes 100 companies building products for scale. Currently, he works at Zoomcar as a Principal Engineer leading the ZAP tech team.