For Systems of Innovation, well, the whole point is to demonstrate how new technologies may positively impact your application portfolio. The purpose is to achieve organizational experience with the technology. These technologies aren't picked willy-nilly - they're serious contenders for developing applications moving forward.
For Systems of Distinction, the point is the features being developed are unique in the market amongst your competitors and/or provide you a key competitive advantage in your market. Failure represents a high business risk. You'd favor existing, well-known architectures, but you may believe newer technologies could yield much better results. The typical strategy is to take the riskiest part of the implementation and develop it using the newer technology. If that goes well, then proceed with the newer technology. Otherwise stick with the tried-and-true.
For all other projects outside of the above, stick with your current technology stack. The strategy is to get as much delivered with the least amount of implementation risk and having the fewest operational surprises and business disruptions.
Bottom line - technological change needs to be carefully managed in an organization.
For Systems of Innovation, well, the whole point is to demonstrate how new technologies may positively impact your application portfolio. The purpose is to achieve organizational experience with the technology. These technologies aren't picked willy-nilly - they're serious contenders for developing applications moving forward.
For Systems of Distinction, the point is the features being developed are unique in the market amongst your competitors and/or provide you a key competitive advantage in your market. Failure represents a high business risk. You'd favor existing, well-known architectures, but you may believe newer technologies could yield much better results. The typical strategy is to take the riskiest part of the implementation and develop it using the newer technology. If that goes well, then proceed with the newer technology. Otherwise stick with the tried-and-true.
For all other projects outside of the above, stick with your current technology stack. The strategy is to get as much delivered with the least amount of implementation risk and having the fewest operational surprises and business disruptions.
Bottom line - technological change needs to be carefully managed in an organization.