Skip to main content

What is SOA?


SOA:   (Service Oriented Architecture)
  • It is an architectural style that lets multiple software services interact
  • It requires that services interact with one another, but without inter-dependencies
  • Service should be autonomic and loosely coupled 

Why should we go for automating SOA:-
For this question, we need more clarity on the below questions for a well structured application:
  • Does the service respond quickly enough for the intended users?
  • Will the server respond with the correct values?
  • How will the service handle exceptions and illegal values?
  • Is the service stable under expected and unexpected user loads?

Because of all these questions for a product, we’ll go for SOA automation. By using this, we can

  • Reduce the risk in the application (On Upgrade or Deployment of new services)
  • It gives  flexibility to the user to merge large functionalities to generate adhoc applications
  • It is a simple Interface, reduces complexity

Comments

Popular posts from this blog

RPA Implementation Approach

RPA Implementation Approach: 1. Tool Selection o     Based on user requirements, features available in tools, you’ve to select TOOL from mentioned above         2. Process Prioritization o     After successful section of Tool, you’ve to consolidate & prioritize the all processes in current operation. Let’s start automating lowest first and most important to next

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)

RPA Life Cycle

RPA Life Cycle: It is similar to software development life cycle with some minor changes. Technically, we called it as ‘ Life Cycle of a Bot’   Analysis:           ·     RPA Cycle begins from ‘ Analysis ’ phase.           ·     In this, Business Team & RPA Strategist/Architect identifies business process to automate           ·     After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...) Development:          ·       Dev. Team starts working on requirements wrt to Environment.          ·       We called this phase as ‘ Bot Development ’          ·       Based on Tool selection , Limited/No coding is required ...