Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

DevSpace philosophy around microservices architecture #2968

Unanswered
ianfdk-u asked this question in Q&A
Discussion options

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!

You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant

AltStyle によって変換されたページ (->オリジナル) /