Hello everyone. I want to know what you think is better to organize stacks: by service or by feature? Or there is a better way?

I think @Frank might have better answers for this but I think organize them in a way that's easier for your team to understand and visualize. That might be splitting by feature. But you might hit some cases where a couple of features need to share some resources. So in those cases you might pull those common resources out into a separate stack. On the other hand, if your resources are managed by a DevOps team that isn't thinking directly in terms of the features of your app. They might like to organize by keeping certain services together because that's easier for them to understand. I would say this though, the setup we have the guide, where we split by the type of service is mainly for instructive purposes. It's easier to read and understand what's going on for a new user.

no idea if it's the best way, but as a developer, I'm trying to organize my stack by module/feature because it looks more natural to me. As in the services I have a common folder with shared components

Hey Paulo, can you share more details about your services/features? Without knowing the details, the answer is always ’it depends 🙂

Hi Frank, Luis is the one who made the original question 🙂

Thank you for your answers @Jay @Paulo, based on them and analyzing it very well I will follow your idea to organize them by feature, it is more natural and easier to see the interaction between the different components