No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Yes, it's all possible. What's a micro-stack?

YEs, self managed backends have stackreferences that allow you reading data from another stack's outputs

I suggest a good naming convention for the stack names as self managed only support a simple naming convention - there's no concept of owner/project/stack

so you'd need to do something like <http://networking.dev|networking.dev> as a stackname

oh! that's the secret, I was exactly wondering how to do that

then do I have to keep several stacks, one per micro-service?

for instance:
```coreinfra.dev
appone.dev
apptwo.dev```
or all them should share the same `dev` stack?

it depends on what you are using a stack for - if an environment then I'd say yes