---
title: "Comment by Vedran Blazenka on \"Tips For a Better Redux Architecture: Lessons for Enterprise Scale\" | Hashnode"
description: "Question regarding this statement: Specifically, we are currently passing every prop needed down from the Container level. These props are either defined in the"
url: "https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3/comment/5834539df533d193a2e689d4"
---

[Discussion](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3)

Comment [Tips For a Better Redux Architecture: Lessons for Enterprise Scale](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3)

[Vedran Blazenka](https://hashnode.com/@vblazenka)

[Nov 22, 2016](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3/comment/5834539df533d193a2e689d4)

Question regarding this statement:

> Specifically, we are currently passing every prop needed down from the Container level. These props are either defined in the Container or injected via the connect HoC. While this makes organization simple it also means every change or addition of a prop equates to changes to every JSX component in the tree. This gets tiring.

Do you have some kind of solution for this?

I find myself using one container that is connected to Redux store and passing everything to my children. Result of that is a lot of returning in mapStateToProps and mapDispatchToProps.

One logical solution for me is to separate one big container to maybe 2-3 smaller containers for easier tracking of what is imported and connected.

Is there anything else you can advise?

Thanks! :)

[Michael Gilley](https://hashnode.com/@michaelgilley)

[Nov 22, 2016](https://hashnode.com/posts/tips-for-a-better-redux-architecture-lessons-for-enterprise-scale/58327eec23b26d367bf71cd3/comment/5834539df533d193a2e689d4#reply-5834886cf533d193a2e68a41)

Hi @vblazenka . We use many different containers and at each container level have a separate module. Props are not passed into Containers from parents though (except from Providers like react-intl, Redux, or React-router). It makes for a much flatter architecture than having only 1 container BUT there is still the problem of passing things down multiple levels when components get deep. I'm not sure what the fix for this would be and using context is out of the picture. I just might be the price paid for the other benefits of such a design....