A physical architecture has specific technologies and trademarks, but a logical architecture is a system of technological principles that does not. When designing cloud computing architecture, it’s important to see what problems need to be solved. Determining what the acceptable solution will require would be the next step. It is important to look at the databases, storage, compute, etc. This method’s main advantage is that it enables the architect to consider a technological solution’s broad scope more impartially. You will construct the solution around what functions with that particular product and brand when you identify a specific technology or brand of technology.
We choose a certain cloud provider before we comprehend the fundamental business and technical needs (i.e., the issues that the technology must address), and we then go forward with a solution that is native to that particular cloud provider. We must then select technology that adheres to the limitations of a single cloud provider since we made the brand decision too early in the process. The solution will, at best, operate on sub-optimized hardware. We must first select the greatest technology for the task, followed by the best suppliers, in order to properly optimize a solution. It frequently occurs with cloud-based databases that restrict the types of middleware, BI tools, database administration software, etc. Early decision-making restrictions virtually invariably end up being a mistake.
In summary, a logical architecture consists of a concept-based list, configuration, and linkages with technology. You can go to the physical architecture until you have a logical architecture with conceptual answers to a particular problem. Translated another way, connects fundamental technologies in the physical world to abstract technologies in logical architecture. The last contender for the solution is now the physical architecture, but before you proceed with any form of deployment, the technology must still be tested and certified. With this procedure, there will still be hiccups. You could declare a technology notion, for instance, in the logical architecture that does not exist. There may be alternatives and features that certain technologies on the market lack, such as a database that lacks built-in risk analytics for the type and model of database you logically established. Although these problems are uncommon rather than the rule, you will need to modify them. Additionally, cloud architects must have a solid understanding of both relevant technologies and broader technological ideas.
Making rational architecture planning before choosing a certain technology can help you make better choices. Since most architects have particular technologies and preferences, this also eliminates the idea that architects are individuals. They could be biased toward a certain cloud provider, database, security strategy, etc., which leads to a solution that functions but are significantly more expensive than one that is better optimized. Remember that your objective as a cloud architect—or as anybody who derives business solutions from technology—is to develop a solution that provides the organization with the greatest return on investment. To increase your chances of success, start with a logical architecture strategy.