Re:Should that be a microservice? Factors to keep in mind
by lucidone on Sunday April 21, 2019 @08:45AM
(#19711840)
As someone on a dev team with little experience with microservices, including myself initially, you're going to make a big mess before you know how to clean it up. Take eventual consistency seriously. Limit rpc across services as much as possible. Agree on standards and your source of truth as early as possible. CI/CD the small stuff that doesn't matter (linting, test running). Also, have a good integration/e2e testing set up early - mock tests ended up being very brittle for us.
Re:Should that be a microservice? Factors to keep in mind
by not_kurt_godel on Sunday April 21, 2019 @03:47PM
(#19714128)
Agree with all of this, especially:
> have a good integration/e2e testing set up early - mock tests ended up being very brittle for us.
Unfortunately microservices also can make good integration testing difficult when it comes to testing full e2e functionality. The results of testing e2e, by nature, rely on the sum of the services interacting with each other properly, thus creating testing dependencies between services that negate some of the advantages of having separated them in the first place.
Also, when your team architected the microservices originally, how many previous microservices systems had y'all built? I haven't built any and am just trying to get a feel for the learning curve.