These were the main issues we realized in our flows within all departments: Some people came up with alternative ideas for better performance. Every person checked their scenarios which they own. We have a Slack bot that alerts us whenever there is an issue in Airtable modules (API limits). :)įirst, we sat down and looked for every scenario in Integromat and sometimes analyzed the API calls from the logs to have some metrics in front of us.
So we were getting ready but not as fast as we were growing. Integromat - NocoDB Module - Customer Product write Integromat Module.Role-based control is department responsibility (VP Engineering of the Department, Department Head).One database-instance per department (PostgreSQL) - AWS Aurora PostgreSQL.These were the core points we focused on earlier when we already decided on NocoDB as an alternative for Airtable: Still, the performance we gained by the speed of moving fast while we grow was pushed by Airtable. But, we were not 100% ready when the issue occurred, it took a few weeks to solve the problems. So, it's quite important to be ready when you hit the limit. Initially, we planned a sprint for two weeks, created our Kanban board in Jira, identified issues, and scheduled regular meetings for status updates on the tasks.īefore tackling the API limits, we created an Airtable migration plan and focused on certain topics for investigation earlier before we hit the issues. I was representing the user acquisition team. Therefore, we initiated an immediate action squad functioning cross-departments with the lead of Christian (VP Engineering - B2B), Tome (Tech Lead - Customer Product), and Alexander (VP Engineering - Data & Finance). (Andreas Wixler (CTO) initiated the Slack channel for Airtable Action Squad)Īfter we hit the limit, we were no longer able to provide a reliable service to our customers. Today, you will be reading how we tackled Airtable's API limits while the company grows to 10.000 car subscribers since 2019. We started to use Airtable at the early stages as I described in my previous article.
0 kommentar(er)
