On Thu, Feb 13, 2020 at 12:42 PM Methusha Thuraisingam <[email protected]>
wrote:
> Project Description
>
> In WSO2 API Manager, service discovery enables you to get the maximum
> advantage from a microservices architecture. The API Publisher brings all
> endpoint URLs to one place, where you can discover service endpoints from
> one or more systems. When creating an API, you can select the service
> endpoint that is discovered. The initial development is based on Kubernetes
> and this is designed to plug any service discovery system.
>
> For the implementation, we are introducing a new REST API in publisher as
> follows to list down the available services.
>
>
> GET /service-discovery
>
> Response:
>
> {
>
> Kubernetes: {
>
> “List of services in Kubernetes cluster”
>
> }
>
> }
>
I think this feature has dependency on the private jet mode where we define
the kubernetes environments. These services will be fetched from the
configured environments right?
>
>
> In the publisher, we can list down services as follows.
>
>
> Service URL
>
> Properties
>
> http://10.0.0.11:6379
>
> Namespace: default
>
> Service type: Cluster IP
>
> http://10.0.0.12:6379
>
> Namespace: default
>
> Service type: Cluster IP
>
This will be integrated with our endpoint UI. Are we going to show these
properties in an endpoint drop down list?
>
>
> Now users can select one of the services available. Once they save their
> selection that particular service will be fixed as their backend service.
>
> For the API Payload, a new section will be introduced as serviceDiscovery
> to keep the existing service endpoints in the API.
>
Why we require this? Once API creator select the endpoint, there isn't a
need of saving the other service endpoints.
>
> Please go through the description and I highly appreciate your thoughts on
> this $subject.
>
> Thanks!.
>
>
>
> --
> Methusha Thuraisingam | Intern . Engineering | WSO2 Inc.
> 0768035487 | [email protected].
> [image: http://wso2.com/signature] <http://wso2.com/signature>
> http://wso2.com/signature
>
--
*Harsha Kumara*
Technical Lead, WSO2 Inc.
Mobile: +94775505618
Email: [email protected]
Blog: harshcreationz.blogspot.com
GET INTEGRATION AGILE
Integration Agility for Digitally Driven Business
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
