Exploring Multilateral Cloud Computing Security Architectural Design Debt in Terms of Technical Debt

This work identifies various design debt causes in a cloud computing system from various dimensions of design debt. Even though immature, un-ripen coded service accessible over the Internet using the cloud computing paradigm may work fine and be wholly tolerable to the patron; but excess quantities will make a service progression that may lead to extreme specialist of software developers and finally an inflexible product. Delivery of the earliest primary beginning coded service without ripeness or maturity is like going into debts or arrears or due to obligation. A petite tiny debt rates progress so protracted as it is paid or rewarded back punctually with a rewrite/redraft/revising/reworking. The risk arises when the debt is not repaid and settled. Every miniature infinitesimal effort spent on imprecise code reckons as interest on that arrears/debt. Intact engineering business can be brought to be idle under the balance load of an unconsolidated, non-solicit implementation, execution, and performance discharging object-oriented, functional or procedural or otherwise. This work uses refactoring as a solution for the identified debt in the multilateral cloud security architecture to secure the cloud services.