English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Widespread adoption of agile project management, independent delivery withmicroservices, and automated deployment with DevOps has tremendously speedupthe systems development. The real game-changer is continuous integration (CI),continuous delivery, and continuous deployment (CD). Organizations can domultiple releases a day, shortening the test, release, and deployment cyclesfrom weeks to minutes.  Maturity of container technologies like Docker and container orchestrationplatforms like Kubernetes has promoted microservices architecture, especiallyin the cloud-native developments. Various tools are available for setting upCI/CD pipelines. Organizations are moving away from monolith applications andmoving towards microservices-based architectures. Organizations can quicklyaccumulate hundreds of such microservices accessible via applicationprogramming interfaces (APIs).  The primary purpose of these modern methodologies is agility, speed, andreusability. While DevOps offers speed and time to market, agility andreusability may not be guaranteed unless microservices and API's are linked toenterprise-wide stakeholders' needs. The link between business needs andmicroservices/APIs is not well captured nor adequately defined.  In this publication, we describe a structured method to create a logical linkamong APIs and microservices-based agile developments with enterprisestakeholders' needs and viewpoint concerns. This method enables capturing anddocumenting enterprise-wide stakeholders' needs, whether these are businessowners, planners (product owners, architects), designers (developers, DevOpsengineers), or the partners and subscribers of an enterprise.

Linking Stakeholders' Viewpoint Concerns and Microservices-based Architecture