Choice of data stores is closely tied to business use cases. As Rootconf alumni Kiran Jonnalagadda points out, either you pre-empt growth too early without customers to service (thereby leading to capacity planning, costs and code overheads), or you plan on the basis of current users and growth. In either case, there are no right or wrong answers - just experiences and war stories to share.
This meetup – sponsored by Elasticsearch – is about data stores. Talks at the meetup will cover:
- Experience stories and insights about data store choices and why these were chosen for specific business contexts.
- Migration war stories.
Case studies of data stores other than Elasticsearch will be shared. Submit your talk here: https://hasgeek.com/rootconf/elasticsearch-users-meetup-hyderabad/proposals#call-for-proposal
Who should attend:
- Database administrators
- Systems integrators
- Software engineers
- Tech leads
Date: Friday, 16 November
Time: 5:30 PM - 8:00 PM
Venue: ThoughtWorks Hyderabad, Abdul Kalam room, 3rd Floor, Apurupa Silpi, Lingampally Rd, beside H.P. Petrol Bunk, Rajiv Gandhi Nagar area, Hyderabad, Telangana - 500032
The meetup is free to attend. RSVP to confirm your attendance.
About the organizers:
This event is curated and produced by Rootconf. Created in 2012, Rootconf is a community of systems engineers, DevOps, software programmers and network engineers managing infrastructure at scale.
For details, contact HasGeek on email@example.com or +91-7676332020
Supporting utf8 characters in a utf8 mysql table
MySQL’s “utf8” encoding only supports three bytes per character. The real UTF-8 encoding needs up to four bytes per character. After upgrading our app’s rails version in production, we started noticing issues in saving objects in the database because of MySQL’s strict mode. We’ll talk about key learnings, the migration itself and best practises for newer apps.
- How we supported storing utf8 content in our app.
- How upgrading the rails version caused MySQL to run in strict mode causing the problems.
- How we evaluated our options and chose the final solution.
- The actual migration and dealing with ad-hoc issues.
Lead Software Engineer @ Freshworks.