Loading ...

IOA -- is it like SOA? | IOA Knowledge Base Community

Posted in: All Community Discussions    IOA Knowledge Base Community

IOA -- is it like SOA?

Subscribe to RSS
  • rmeyer

    Hello experts!  They seem to be both about architectures - one for infrastructure and the other for software. is there any connection between the 2?


  • Snarkier

    What a great question as the concepts of SOA, microservices and IOA will continue to surface as the move to more distributed services and systems becomes standard practice.

    I'll think through the larger response and come back with a perspective.  

    Thanks again and be right back.

    I have practiced pattern based design for over 20 years and am passionately curious about how technology affects our lives.
  • Snarkier

    Hello again,

    As promised....
    When defining SOA, there are numerous web sites that have good explanations, but I will borrow from Wikipedia’s definitions here https://en.wikipedia.org/wiki/Service-oriented_architecture:

    A service-oriented architecture (SOA) is a style of software design where services are provided to the other components by application components, through a communication protocol over a network. A service is a discrete unit of functionality that can be accessed remotely and acted upon and updated independently, such as retrieving a credit card statement online.

    A service has four properties according to one of many definitions of SOA:
    • It logically represents a business activity with a specified outcome.
    • It is self-contained.
    • It is a black box for its consumers.
    • It may consist of other underlying services

    Microservices Architecture is a variant of the (SOA) architectural style that structures an application as a collection of loosely coupled services. In microservices architecture, services should be fine-grained and the protocols should be lightweight. Fine grained is of course related to the business domain, but we are seeing that in addition to encapsulating processing, microservices tend to have their own data repository whose scope is focused solely on the microservice in question.

    Both approaches to application architecture assume distributed deployment as fundamental. Both approaches focus on minimizing the impact of change. And both approaches have existed before IOA became codified in 2015.  Both approaches are greatly enhanced when using the principles of IOA. 

    Now for the IOA part....

    IOA is an architecture approach that emerged as a result of studying hundreds of deployments at Equinix colocation hubs

    IOA principles solve for a set of fundamental challenges all distribute applications experience when addressing the user needs in a digital economy

    • The limitations of physics as it relates to application response time
    • The exponential  increase in traffic volume and the accumulation of data required for engagement  at the edge where users and partners are
    • The need to apply local compliance regulations in a timely manner across regions
    • IOA addresses these problems through a set of tactics that can be briefly summarized as
      • Establishing a local communication hub control point where users and partners are, ensuring that local traffic is routed locally improving performance
      • Establishing a multicloud control point so inter-cloud communication is optimized at minimal cost
      • Move services and required data to the  edge to improve application response time in a distributed environment
      • Ensure that each digital edge node is secured with border controls and inspection zones
    Finally, as all these are architectures are logical -- the basic principles of all of these architectures are expressed while being independent of vendors, products and technologies.  

    I hope this is helpful and puts things into perspective for you (and others who read this).
    I have practiced pattern based design for over 20 years and am passionately curious about how technology affects our lives.
Page 1 of 1 (3 items)