| 失效链接处理 |
|
Service Mesh and Related Microservice Technologies in ONAP PDF 下载
本站整理下载：
相关截图：
主要内容：
Challenges in ONAP Micro Service Architecture
- Need for client libraries for infrastructure services
• Consumes lot of time by each project; Error prone; Mismatch in capabilities across projects.
• Few examples:
• Integration of Authentication and Authorization by every service; Mutual-TLS enablement by every service;
Storing Secrets securely by each service.
- Polyglot challenges
• ONAP services are written in various languages (Java, Python etc.)
• Client libraries in various languages and language specific restrictions to use some features uniformly.
- Visibility of inter-service data for trouble shooting and any kind of analytics & and also tracing the
requests across projects.
• If Mutual-TLS implemented from the service itself, any troubleshooting that is needed during operations is tough
and expect code changes in every project for debugging.
- Service Discovery, Load balancing of requests among services, Circuit breaking, Health Checks and API
routing etc. require changes in every ONAP service container.
- No easy way to address rolling updates and ensuring continuous operations (versioning etc.)
- Achieving security is dependent on ONAP projects (System call filtering, Storing keys securely in
TPM/SGX, Keeping password secure etc.)
• Solution Direction – Service Mesh
- Eliminate or reduce micro-service infrastructure level tasks in ONAP services
- Ensure that ONAP Services have only the business logic of that service
|
| Java1234官方群25： | 
|
| Java1234官方群25： | 838462530 |
苏公网安备 32061202001004号
