Subject: Proposal: Decentralized Hub-and-Spoke Design using Network Connectivity Center (NCC) #3309
hassannmoussaa
started this conversation in
General
Replies: 2 comments 1 reply
-
|
@ludoo what you think ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Yeah end goal is a flexible yet maintainable network design. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Proposal: Decentralized Hub-and-Spoke Design using Network Connectivity Center (NCC)
Hi everyone,
I'd like to open a discussion around a potential new stage 2 networking design proposal towards a decentralized hub-and-spoke approach, leveraging Google Cloud’s Network Connectivity Center (NCC).
This idea is still in early stages, and I want to gather feedback and perspectives from the team before drafting a formal PR or design document. So we may collaborate all on that !
The goal here is to:
Increase resiliency and scalability of our fabric.
Reduce single points of failure by moving away from a purely centralized model.
Use NCC’s capabilities to simplify interconnectivity across regions, spokes, and on-premise locations.
We may benefit from managed IPS/IDS recently announced GA in google cloud for a unified security approach.
Introducing this as a blueprint in the Fast context will help users follow latest design trends and recommendations also.
I’d appreciate your thoughts, suggestions, concerns, or any related experiences. Let’s use this thread to collaborate before moving into formal planning or implementation.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions