TM Forum Community

Expand all | Collapse all

Is your solution, architecture modern? How will you decide that.

  • 1.  Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 15 days ago

    Based on my experience, I am trying to list down key features which can help in deciding whether technical solution is modern, future-proof

    1. Model driven – model drive solution will allow faster T2M, bridge gas been business and IT and finally make solution technology or vendor agnostic
    2. API/Micro service complaint – architecture must be loosely coupled hence use of APIs/Micro service will allow scalability, re-usability and seamless integration
    3. Scalable data model – underlying data model if any, must be scalable and future proof else data model can become serious bottleneck with frequent changes
    4. Aligned to open standards – alignment to open standards will avoid any vendor locking and speed up innovation. However if solution is being built upon some COTS, COST must be chosen carefully, proprietary standards must be avoided.
    5. User centered interface – User interface must be intuitive and easy to use. New operation users should be able to learn and adopt UI with minimal effort.
    6. Cloud ready/ Cloud native – Cloud based solution will be cost effective and scalable.

     

    I am very keen to receive inputs/views to make above list comprehensive.  Idea is to build a checklist to qualify a solution modern or something which can be refereed while starting a greenfield implementation.

     

    Note – I am not getting into execution methodologies like Agile/Devops etc. 


    #DigitalEcosystems

    ------------------------------
    Mohit Prabhat Tyagi
    OSS Portfolio Lead, Program Manager
    Infosys
    ------------------------------


  • 2.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 14 days ago
    I would add
    • Are you using best solution components, for the purpose?
    You may actually replace your point (6) with this, as not everything is best placed in a Cloud.
    Additionally, it is important to distinguish between market hype / "fashion" and fit for purpose.

    ------------------------------
    Sergey Zak
    Australia
    ------------------------------



  • 3.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    Thanks for suggestion.
    yes i totally agree that we dont need to over-engineer based on market hype/fashion.

    ------------------------------
    Mohit Prabhat Tyagi
    Infosys
    ------------------------------



  • 4.  RE: Is your solution, architecture modern? How will you decide that.

    Posted 13 days ago
    The ODA is a starting place for thinking about this. From the recent whitepaper: "loosely coupled, cloud native, data and AI-driven; made up of standard components which can be easily procured and deployed, without the need for customization".
    https://www.tmforum.org/resources/whitepapers/a-future-vision-for-the-software-market-that-the-telecom-industry-needs-to-survive-and-thrive/

    ------------------------------
    James Crawshaw
    Heavy Reading
    ------------------------------



  • 5.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    Thanks James, very informative and relevant whitepaper.
    Certainly "SOFTWARE MARKETPLACE" is way to go. Many service providers are doing lot of in house development, trying to build next generation components for OSS/BSS and having a vision to build public or private market place. I am trying to put up a perspective for these software components.
    I shall look at ODA in detail too.

    ------------------------------
    Mohit Prabhat Tyagi
    Infosys
    ------------------------------



  • 6.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    I think following are some of the important factors which would decide if the architecture is modern:
    1. Alignment with ODA  -  Systems of Engagement, Systems of Records and Systems of Insights decoupling through Open API Layer
    2. Use of Open APIs - So as to standardize the integration and to be able to deliver any sort of product ordering as Open APIs are agnostic to the same.
    3. Cloud Native Architecture - Container based architecture which can be scaled automatically to cope with large volume which would it needs to cater with the evolution of 5G
    4. Support for 5G charging and slice management functionality

    Regards,
    Vivek

    ------------------------------
    Vivek Gulavani
    Oracle Corporation
    ------------------------------



  • 7.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    Thanks Vivek
    Our thoughts are aligned, I am trying to put generic guidelines so not putting anything very specific to telcom like your point 5.

    ------------------------------
    Mohit Prabhat Tyagi
    Infosys
    ------------------------------



  • 8.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    ​Mohit, a few of comments/suggestions:

    1. Regarding "Model driven", I suggest to rephrase or extend: what model(s) are we talking about? You mentioned technology or vendor agnostic, so I suggest something "solution comprised of standard replaceable components integrated via a well documented standard API, such as Open API".
    (Model is a broad word and might mislead to "commercial model", "data model", etc

    2. API/Micro service compliance, I suggest to just leave API in here. Microservices is really just an specific way of building internal systems architecture. It fits certain purpose, such as highly-available applications like portals, etc, where support for high-availability, auto-scalability is needed. The loosely coupled architecture may or may not be based on micro-services.

    3. Suggest to add: Scalable data model, flexible processes configuration, configur able business rules, preferred low-code environment to accommodate frequent changes

    5. Can also add "intuitive" - so to promote fast adoption and self-learning by users

    6. This really needs elaboration, do we mean "Ready to be deployed in either public, hybrid or private cloud infrastructure" ? Or do we mean "SaaS software'?
    Cloud means so many different things nowadays.. Mostly the confusion is in infrastructure-related questions and Saas vs enterprise commercial models.

    Regards,
    Andrey


    ------------------------------
    Andrey Svalov
    T-Mobile Nederland BV
    ------------------------------



  • 9.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago

    Thanks a lot Andrey for detailed response and recommendations.

     Please see my comments inline. 

    1. Regarding "Model driven", I suggest to rephrase or extend: what model(s) are we talking about? You mentioned technology or vendor agnostic, so I suggest something "solution comprised of standard replaceable components integrated via a well documented standard API, such as Open API".
      (Model is a broad word and might mislead to "commercial model", "data model", etc

             <Mohit: By Model driven, I mean use of various data modelling standards like TOSCA for service templates, YANG for resource templates, BPMN 2.0 for workflow templates
             etc. This will bridge gap been business/planning/network teams and IT and let not-IT ppl use data models designed for them.

             My Point 2 and Point 4 are addressing use of APIs and open standards like Open API etc. which will finally result in standard replaceable components and smooth integration.>

            2. API/Micro service compliance, I suggest to just leave API in here. Microservices is really just an specific way of building internal systems architecture. It fits certain purpose,
           such as highly-available applications like portals, etc, where support for high-availability, auto-scalability is needed. The loosely coupled architecture may or may not be based
           on micro-services.
          <Mohit: makes sense, idea is to build a loosely coupled architecture.>

    1. Suggest to add: Scalable data model, flexible processes configuration, configurable business rules, preferred low-code environment to accommodate frequent changes
      <Mohit: totally agree. My Point 1 – data model driven is also pointing to configuration driven, low-code solution.>
    2. Can also add "intuitive" - so to promote fast adoption and self-learning by users
      <Mohit: point taken>
    3. This really needs elaboration, do we mean "Ready to be deployed in either public, hybrid or private cloud infrastructure" ? Or do we mean "SaaS software'?
      Cloud means so many different things nowadays.. Mostly the confusion is in infrastructure-related questions and Saas vs enterprise commercial models.

              <Mohit: since I was compiling from Telco side, I meant ready to be deployed in either public, hybrid or private cloud infrastructure.

               But from vendor viewpoint, Saas is picking up. I shall rephrase this point to cover all aspects.>



    ------------------------------
    Mohit Prabhat Tyagi
    Infosys
    ------------------------------



  • 10.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    Hi Mohit

    I see. Regarding first point, still suggest to consider "industry standards based, such as YANG, TOSCA, etc" to make it more concrete. I'm not a native English speaker, but model and standards sound like different things to me..

    (Thanks for the detailed response, appreciate your attention to it)

    Regards,
    Andrey

    ------------------------------
    Andrey Svalov
    T-Mobile Nederland BV
    ------------------------------



  • 11.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 10 days ago
    I can see small typo error and not able to edit post. Read point 1 as below:
    Model driven – model drive solution will allow faster T2M, bridge gap been business and IT and finally make solution technology or vendor agnostic

    ------------------------------
    Mohit Prabhat Tyagi
    Infosys
    ------------------------------



  • 12.  RE: Is your solution, architecture modern? How will you decide that.

    Posted 10 days ago
    I would add to what extent it is supporting (or future proof)  the famous 4th industrial revolution, in terms of automation & AI, massive data sets (big data), IoT, Blockchain etc. I do agree that standards normally comes with a roadmap for their evolvement & many adapt in their roadmaps new technologies yet many changes would be still required to keep up with the industrial challenges & emerging cost changes that are being driven by other factors ..

    hope this help.

    ------------------------------
    Mohammed Al-Kalbani
    Ooredoo Oman
    ------------------------------



  • 13.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 9 days ago
    Remember that the Forum also has:

    Both of these are indications to the market place that your architecture is modern...

    Also, customers will check whether individuals within a company are trained and certified to develop and deliver Open APIs and understand the ODA and can put it into practice.  These individual are shown on your Member Profile page, along with your Product Conformance and Open API certifications:
    If in doubt, talk with your Engagement Manager, who is listed on your Member Profile page.
    Dave

    ------------------------------
    Dave Riches
    TM Forum
    Cleaner
    +44 774 811 8071
    driches@tmforum.org
    ------------------------------



  • 14.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 8 days ago
    Do we also need to add  -  # Security
                                                   # Business intelligence or data Science/ML/DL​​(Automation/AI) or you feel it by product of  your point - 3 scalable data model ?

    ------------------------------
    satyajit sethy
    Netcracker Technology
    ------------------------------



  • 15.  RE: Is your solution, architecture modern? How will you decide that.

    Posted 4 days ago
    Hi,

    Excellent, but let me purpose to add Dev Security Ops and Governance maturity Model sections...

    Best Regards
    EA

    ------------------------------
    Mouaad Hayadi
    Entreprise Architect
    www.syntechnologie.net
    ------------------------------



  • 16.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 2 days ago
    Interesting thread..

    In my view before jumping into the core Architecture jargon, I would suggest to go one step back!!
    Modern Architecture Can not be generalized or Standardized. It is purely driven by the values an Architect bringing on the table for the Organization.

    In one Word I can say it's a transformation Towards the Organization Vision and Mission.

    But to some extend the basic ingredients are:

    • Cloud Native
    • Model Driven
    • APIfication

    Thanks
    Amit
    Solution Architect


    ------------------------------
    Amit singh
    Tata Consultancy Services
    ------------------------------



  • 17.  RE: Is your solution, architecture modern? How will you decide that.

    TM Forum Member
    Posted 21 hours ago

    This is very interesting topic. Amit, thanks to bring this discuss to the group!

    Honestly, I feel very hard to define what modern architecture is after working in this industry for 20+ years in both R&D and solution side.

    First, software/product architecture is very different from solution architecture. By reading the messages above, I got the feeling this is mainly about solution architecture though, there are items applicable to both software/product architecture and solution architecture. For example, model driven, coupling, etc.

    Second, based on my experience (I might be wrong) the key features for a solution to be modern and future prove are:
    1. standard based software product and API (this included data model, interface, process, etc.)
        This would make the solution modern because the standards are moving forward and keep themselves modern, and future prove because new standards will continue to come out. This also will prevent vendor locking or at least make it easier to switch vendor or integrate with multiple vendors. Standard based software also can enable vendor agnostics for assurance, fulfillment, data analysis, etc.

    2. cloud native, cloud ready is not good enough, has to be could native or has roadmap to migrate to cloud native
         The key difference is that cloud native system can be deployed to either small or large logical server.

    3. symmetric distributed system architecture therefore symmetric HA and DR
         As solutions for OSS/BSS are very complex with large amount of code and data processing huge amount of entities, high scalability, performance, reliability, etc. are must. Active-standby HA/DR are just waste of resource and gives low confidence if the standby would work when the active goes down. With symmetric distributed architecture, system can scale out easily to increase performance, reliability, and scalability.

    4. component-oriented with model driven software
        In this industry, how to make solution mature/reliable and also flexible (I mean like requirements come in today, the patch ready tomorrow or next week, not months later) has been a big challenge for long time. Component-oriented with model driven can resolve this with peace of mind.

    Other features seem have far less importance compare to above, or they actually belong to above items.

    This is just one opinion. I'd love to discuss and learn from you all.



    ------------------------------
    Fazhong (David) Deng
    OSSEra
    ------------------------------