[Metricon]

As CTO, your primary responsibility is leadership, so assuming you have other development staff, your Principle Engineer/Senior Architect/Lead Developer (or multiples of these in a larger organization) should be providing you with technical options. Your job should be to weight the pros and cons of each within a larger perspective of resource impacts and return on investment. The technical solutioning should be delegated and then affirmed by your direction.

If the CTO title is more ceremonial (or your organization is very small) and you are actual performing the role of the most senior developer, know that there is no “right” solution to any software development task. Any working solution outweighs any theoretical optimal solution. The only real metric that matters is that each time you make a decision that it is better than the last one; where better is an amalgamation of (personnel * knowledge * skills * metrics ) / time available.