Modeling Microservices and APIs in the CSDM Recorded Feb 29th 2024
ฝัง
- เผยแพร่เมื่อ 30 ก.ย. 2024
- Link to community post and content: www.servicenow...
Speakers:
Mark Bodman - Sr. Product Manager at ServiceNow
Richard Best - IT Architect at Banner Health
Things you will learn:
The current challenges with API and Microservice definition modeling in CSDM
How to address challenges with API and Microservice definitions today
What’s coming for APIs and Microservices
Considerations for APIs and Microservices in various CSDM domains
Does anyone have a suggestion for how to model VMware (on-prem HCI "Vm hosting" service) - separate from Windows management and generic 'hosting/compute' - would this just be a service offering under 'hosting/computer' Technical Service?
I love the example models, just surprised there's not one for VMWare or other hypervisor environments, linked to the TS/TSO/Appservice (i think of a VMware cluster as an application service, such that it runs as a cohesive system with dynamic parts, but someone has to manage it) via some 'VMWare administration' TSO - but then what 'offerings' do we put out there for 'request a new VM'?
I feel like there are a couple things which may have gotten confused during the Acuity diagram portion. My interpretation is the the layers from top to bottom are:
1) Business Application
2) Application Services
3) Application CI's (Tomcat, Apache, DB instances, etc.)
4) Server CI's
The fact that some of the application CI's are listed as "Acuity Connect Prod XYZ Server" is more of a descriptor, but they would in reality be Web/Application server application / Database instance CI's and are contained within their respective Application Services.
I may be incorrect, but if not I wanted to try can clarify some of the comments around that section.
Excellent Mark... So, finally we have two points of views in the New Approach about How to manage APIs, right. We have the Operational Standpoint with new classes or extensions that even we can discover because are CIs, and the Design Standpoint where we have a new capability for the APM product that aims to manage the API Lifecycle... Is my understanding correct?