Soa Governance Tools – Cloud Computing Types

Why SOA using Cloud Requires a New Approach to Testing

CloudMan Cloud Architecture, Cloud Services, SOA Governance October 14, 2013April 15, 2018Lightweight Soa Governance, SOA, Soa Data Governance, Soa Governance Activities, Soa Governance And Management, Soa Governance Architecture, Soa Governance Benefits, Soa Governance Best Practices, Soa Governance Certification, Soa Governance Challenges, Soa Governance Checklist, Soa Governance Concepts, Soa Governance Definition, Soa Governance Framework, Soa Governance In Action, Soa Governance Lifecycle, Soa Governance Model, Soa Governance Model Example, Soa Governance Principles, Soa Governance Software, Soa Governance Tools

SOA Governance is a Concept used for Activities Related to Exercising Control over Services in a Service-Oriented Architecture (SOA)

One viewpoint, from IBM and others, is that SOA governance is an extension (subset) of IT governance which itself is an extension of corporate governance.

So, why is SOA making use of cloud computing so unusual that we need a alternative technique to testing? As I have actually been stating on this blog site, very many of the exact same patterns around testing a distributed computing system, such as a SOA, are appropriate here. We are not asking you to test that in a different way; only to consider a few brand-new possibilities.

There are some clear screening differences to note when cloud computing enters the mix.Initially, we do not own nor control the cloud computing-based systems, therefore we have to deal with what they offer us, consisting of the restrictions, and typically can’t change it. Hence, we can’t do some types of testing such as finding the saturation points of the cloud computing platform to identify the upward constraints on scaling, or effort to figure out ways to crash the cloud computing system.

That kind of testing might get you a nasty email. Or, white box testing the underlying platform or services, suggesting seeing the code, is also, not supported by most cloud computing service providers, but clearly something you can do if you possess and regulate the systems under test.

Second, the patterns of use are going to be various, including how one system interacts with another, from business to shadow. Typically, we test systems that are on-premise, and almost never ever test a system that we can not see nor touch. This consists of problems with Internet connectivity.Third, we are checking systems that are contractually obligated to offer computing service to our architecture, and hence we require a means to confirm that those services are being offered now, and into the future. Therefore, testing handles a legal element, because if you find that the service is not being delivered in the manner outlined in the contract, you can act.

Finally, cloud computing is fairly new. As such, IT is a bit suspicious about the absence of control. Extensive and well-defined testing, will eliminate most of those fears. We have to be hyper diligent to decrease the opportunities of failure, and work around the fear of what’s brand-new.

SOA Governance

When Thinking SOA Governance, Think Macro and Micro

CloudMan Cloud Architecture, Cloud Services, Service-Oriented Architecture, SOA Governance October 13, 2013April 15, 2018Oracle Soa Policies, Policies In Soa, Soa Governance And Management, Soa Governance Best Practices, Soa Governance Business Benefits, Soa Governance Concepts, Soa Governance Definition, Soa Governance Deliverables, Soa Governance Framework, Soa Governance Guiding Principles, Soa Governance In Action, Soa Governance Open Source Tools, Soa Governance Overview, Soa Governance Policies, Soa Governance Process, Soa Governance Process Flow, Soa Governance Security, Soa Governance Tools, Soa No Policy, Soa Operational Governance, Soa Policies, Soa Policies And Procedures, Soa Policy Definition, Soa Refund Policy, Soa Runtime Policies, Soa Security Policies, Soa Service Policy

Policies, as connected to governance, are declarative electronic regulations that define the right habits of the services.

Nevertheless, they can be guidelines that are not digitally implemented. An example would be policies produced by IT leaders who produce guidelines that everyone have to follow, but the policies are not automated. Or, they can be policies that enforce the appropriate behavior during service execution, generally enforced electronically utilizing governance technology. Both are very important, and thus why we talk about authorities as things that might exist inside or outside of governance innovation.

For our purposes, we can call policies that are more basic in nature macro policies, and policies that are certain to a certain service as micro policies.

Macro Policies

Macro policies are those policies that IT leaders generally produce, such as the venture designer, to address bigger sweeping issues that cover lots of services, the information, the procedures, and the applications. Examples of macro policies include:

• All metadata must adhere to an authorized semantic model, on-premise and cloud computing-based.
• All services should return a response in.05 seconds for on-premise and.10 for cloud computing-based.
• Modifications to procedures have actually to be authorized by a magnate.
• All services should be built using Java.

The idea is that we have some general regulations that control how the system is developed, redeveloped, and monitored. Therefore, macro authorities do indeed exist as well-known easy guidelines, such as the ones detailed above, or set processes that must be followed. For instance, there could be a process to address how the data source is altered, consisting of 20 actions that should be followed, from initiation of the change to acceptance testing. An additional example is the procedure of registering a brand-new user on the cloud computing platform. Or, any procedure that minimizes operational threats.

Many tend to roll their eyes at these kinds of controls that are placed around automation. I make sure you have many that exist within your IT store now. They could also push back on extending these governance principles to cloud computing. Nevertheless, the core value of executing macro policies is to reduce danger and save cash.

The trick is to strike a balance in between too many macro policies that hurt efficiency, or too few that raise the chance that something bad will occur. Not an easy thing, but a good rule of thumb is that your IT department should spend around 5 percent of their time handling problems around macro authorities. If you spend more time than that, maybe you’re over-governing. Less than that, or if you have catastrophe after catastrophe occur, perhaps you can put in more macro policies to put even more procedures around the management of IT resources, on-premise or cloud computing-based.

Micro Policies

Micro or service-based authorities typically take care of a policy circumstances around a specific service, process, or information element. They are associated with macro policies because macro policies define exactly what has to be done, whereas the micro policies specify how a policy is carried out at the most affordable level of granularity.

Examples of micro policies consist of:

• Only those from HR can take advantage of Get_Sal_Info services.
• No even more than 1 application, service, or process at a time can access the Update_Customer_Data service.
• The Sales_Amount information element can only be updated by the DBA, and not the designers.
• The response time from the get_customer_credit service have to be less than.0001 seconds.

Micro policies are extremely particular, and usually destined for execution within service governance innovation that can track and implement these kinds of policies.

SOA Governance