Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

Make Legacy Applications OpenNESS-aware #65

Open
git-abhijit opened this issue Jun 24, 2021 · 4 comments
Open

Make Legacy Applications OpenNESS-aware #65

git-abhijit opened this issue Jun 24, 2021 · 4 comments

Comments

@git-abhijit
Copy link

Hi,
Please share some more details on how the wrapper code will work for Service Discovery, subscription and other EAA features.

Questions :

  1. The wrapper code will implement all the API's ? Please share a sample code implementing all the features.
  2. Can the design be implemented as a side car application for the legacy application.

Regards
Abhijit

@amr-mokhtar
Copy link
Contributor

Hi @git-abhijit,

  1. It is up to the app vendor to design which APIs are useful for its business logic.
  2. Yes, a legacy application can be interfaced with the EAA and its service discovery by implementing a sidecar. We've done something similar with the OpenNESS video analytics services. See https://github.com/otcshare/edgeservices/tree/master/edgecontroller/vas-sidecar

@git-abhijit
Copy link
Author

Hi @amr-mokhtar

Thank you sharing the details.

One help , the above link is giving 404 error for me , can you share me another link.
Thank you very much.

Regards
Abhijit

@archie951
Copy link
Contributor

@git-abhijit
Copy link
Author

@archie951 Thanks. I will go through the code.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants