Summary

In this chapter, you reviewed, purely from an architecture standpoint, how quality requirements are critical to the success of the API platform. Hence, it is pertinent to recommend that, during the API development lifecycle stages, you prioritize any architectural stories that are part of the backlog, along with any functional stories. This, however, requires executive buy-in for the strategy, and manpower investment to support the approach. Quality outcomes are dependent on the culture of the team.

We also briefly touched on the topics of API security, reliability, availability, and performance. You now understand how maintainability is linked to availability and reliability, and why you must be careful about your choice of the appropriate levels of reliability.

There is always a trade-off between cost optimization, performance, and reliability. Hence, you should evangelize within your teams on how optimal service reliability can be achieved by adopting SRE practices...