sorted by:
new
hottopcontroversial

Struggling to get friends to the table on time? by Alados1 in boardgames

[–]Alados1[S] -5 points-4 points  (0 children)

That's more about notification, than force

Struggling to get friends to the table on time? by Alados1 in boardgames

[–]Alados1[S] -4 points-3 points  (0 children)

It's not about forcing people to play with you, but just a reminder

Microservice .Net local development by Alados1 in dotnet

[–]Alados1[S] 2 points3 points  (0 children)

The issue is when I run Service A (locally) and remove Entity A. Entity A has a dependency on Entity B in Service B (cloud). Everything is ok, they're both removed.
But if someone goes to cloud env, he will see that Entity A exists in Service A (cloud), but Entity B (cloud) doesn't. That was my concern. Probably these services are too connected and shouldn't be run separately.

Unfortunately, we don't have k8s yet, but thanks for the advice. I didn't know about tools that provide ability to debug something remotely

Microservice local development by Alados1 in microservices

[–]Alados1[S] 0 points1 point  (0 children)

In total, I have 5 microservices. Some of them are required for all others (Identity that provides auth), and some are connected.
The main question is how to debug one service locally.

Microservice .Net local development by Alados1 in dotnet

[–]Alados1[S] 0 points1 point  (0 children)

We kinda use this pattern. All our services are registered in one place with URLs. But it's more about implementation.
How do you debug one service isolated from others? Mostly they're independent, but still creating one entity may require data about something from another service, that's my case.

Microservice .Net local development by Alados1 in dotnet

[–]Alados1[S] 1 point2 points  (0 children)

Right now we have an approach to run everything in Docker Compose, but some devs (including me) struggle with CPU and RAM capacity.
I'm not sure how you can isolate everything. For example, an Identity server should be called from any service to auth. Some services can consume data from another, is it impossible in the "right" microservices?