Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessing library api from another library domain #113

Open
Vevl opened this issue Jul 26, 2022 · 1 comment
Open

Accessing library api from another library domain #113

Vevl opened this issue Jul 26, 2022 · 1 comment

Comments

@Vevl
Copy link

Vevl commented Jul 26, 2022

Hello @manfredsteyer, at first thanks!! it was a big pleasure for me to study your materials.

Maybe I didn't understand it well but when I'm using default boundaries from the init generator there is a restriction that only type APP can access type API.

image

How then it should be possible to access API of one domain in another as mentioned in next img --

image

I can't find any information about this specific part of DDD.

Thanks.

@PopePAF
Copy link

PopePAF commented Nov 2, 2022

I just found some Info about this here

So note that: "Access to APIs such as catalog-api must be explicitly granted to individual domains."
and: "In addition, this example also shows the domain Ordering which, according to the context mapping, has access to the CatalogApi. For this, the example uses a name prefix to make sure that only selected libraries are allowed to access the api."

see: { "sourceTag": "name:ordering-feature", "onlyDependOnLibsWithTags": ["name:catalog-api"] }

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

No branches or pull requests

2 participants