Throughout my profession as a practitioner and instructor of cloud architecture and general business architecture, I’ve concentrated on the difference between rational and physical architectures.It’s clear what
they comprise: A logical architecture is a structure of technology principles that does not name specific technologies or brands, while a physical architecture does include specific technologies and brands.When I develop a cloud computing architecture, I first
ask what problems need to be solved. I then identify what an appropriate service will need. Next, I list the items that need to be part of the architecture and their relationships to each other: databases, middleware, encryption, storage, compute, application development, and so on. Again, no specific innovations, only technological ideas that can add to solving the overall problems.The primary advantage to this technique is that it enables the designer to believe more objectively about a general technical option. When you name a particular innovation or brand name of technology, you’ll construct the service around what deal with that specific product and brand.We have actually been making this mistake with public cloud companies for several years. We pick a specific supplier prior to understanding the core company and technical requirements(aka, the problems the technology should resolve), and then we continue with an option that’s belonging to that specific cloud company. By choosing the brand name too early in the process, we must then choose technology that fits within the constraints of a single cloud provider. Best case, the solution will run on underoptimized innovation. To fully enhance a solution, we need to pick the best innovation for the job and then select the very best providers.This is the greatest error I see designers make these days: choosing public clouds before they understand and understand the problem.
It occurs usually with cloud-based databases that restrict the brands of middleware, business intelligence systems, database admin tools, and so on. Restricting your options too early in the preparation procedure usually becomes a mistake. Sadly, companies frequently wind up with a cloud architecture that works.”It works “does not explain an optimum solution. The functional-yet-less-optimal architecture will provide far less value than one that leverages the best technology to solve the particular company problems at hand.To wrap-up, a sensible architecture contains a list, setup, and correlations with technology as principles. When you have a rational architecture with conceptual solutions to specific problems, then and just then do you relocate to the physical architecture. To put it simply, map conceptual technologies in the sensible architecture to actual technologies in the physical. The physical architecture ends up being the supreme option prospect, however the technology should still be verified with screening prior to you move to any sort of deployment.There will still be bumps in the road with this process. For example, you may define a technology concept in the rational architecture that does not exist. Particular innovations on the marketplace may lack particular options and features, such as a database that does not have built-in risk analytics for the type and design of database you realistically specified. You’ll need to change, however these concerns are the exception instead of the rule.Also, cloud designers require to have a working knowledge of general innovation ideas as well as real innovations that can map to these concepts.If you do logical architecture planning before devoting to a specific innovation, you’ll make better choices. This likewise gets rid of the” designers are individuals”element considering that most architects have technology choices and favorites. They might have a bias for a particular cloud supplier, database, security technique, etc,
which winds up being a solution that works however is much more expensive than a more optimized one. Remember that your goal as a cloud architect– or as anyone who defines service solutions from innovation– is to create a service that returns the most value to business. Use the sensible architecture approach first to offer yourself a higher opportunity to reach that goal. Copyright © 2022 IDG Communications, Inc.
Source
