DevSpace philosophy around microservices architecture

[ianfdk-u]

Hi,

Our team would like to experiment with DevSpace as a way to let devs test their changes in the cluster directly.

I understand that using dependencies would allow us to deploy multiple services together so they can all work with each other.

But what if I would like to avoid having to create "the whole world" to test a simple change in one service?

• Does that simply go against the DevSpace philosophy / would it be highly discouraged?
• If not, are there best practices around putting in place the sort of traffic-splitting required to achieve my goal?

Any tips/advice/pieces of wisdom would be appreciated.

Cheers!