I'm working on a proof of concept for a new content understanding service in Azure. I set up a process that involves analyzing audio recordings from a contact center, triggering logic apps for processing, and saving results to CosmosDB. Everything seems to work fine without any bottlenecks.
My question is about deciding when a solution is 'good enough' for production. Should I just move forward with what I've built, or should I look for improvements or anticipatory changes? I'm torn between continuing to perfect my solution and the saying 'don't fix what isn't broken.' What factors should I consider to know if my implementation is solid enough to put into production without overthinking it?
1 Answer
It all starts with your requirements. If your solution meets them, then it's good to go! If it ends up being too complicated or costly, you can always plan for an improved version later on. For now, focus on what you've accomplished!
That's probably my challenge too; I worry it won't scale or that it’s too much of a patchwork solution once it's live. So, I guess I should stick to my criteria and only improve if issues arise.