Hasgeek survey; Rootconf Cloud Costs conference announcement The audience research team at Hasgeek has started a survey to understand the Rootconf community better, and what individuals expect from memberships on <hasg… more
How do you select datastores and be aware of their limitations when applied to the problem at hand? Are there misconceptions you wish someone had cleared for you as you started on your journey of scaling with datastores?
Choosing data stores for your use cases conference will help you understand:
- Running datastores at scale - and tuning, debugging and operations.
- Solving specific use cases with a certain datastore.
- Data modelling and developer experience with datastore.
Senior infrastructure and software engineers from Farfetch, Aerospike, Zeotap, eightfold.ai, LinkedIn and Tesco engineering will share war stories and their learnings with practitioners in the audience.
View schedule at https://hasgeek.com/rootconf/choosing-datastores/schedule
Gotchas! You Created A Many To Many Relationship Without Timestamp
When we started WorkIndia we just thought of shipping features out nothing else
We took decisions around data modelling making our system very configurable and apply generalisation principles for root models and specialisation for leaf models. Now, after 4 years down the line when we created our data lake based on Debezium based Sync Source connectors we faced challenges due to ORM modelling not adding timestamp by default in the models making reconsilation engine always go out of sync
What did we do to fix it on short term?
What did we plan to fix in long term?