News for hackers. Stuff that matters.
Re:IT Runs on Java 8 by jayd16 on Saturday May 11, 2019 @12:23PM (#19886907)
Unlike the others, I'm going to disagree with what you've said. If you have a mono-repo set up you can develop like it's a monolith but with the added benefit that you don't have deploy the whole macro-service at once.

I think people are just spinning up a bunch of unorganized services and calling them micro and then complaining about it.

If you're on a small team that can build a clean monolith, the work to make them microservices is imo pretty trivial.

Re:IT Runs on Java 8 by pojzon on Monday May 13, 2019 @03:32AM (#19896996)
The main point was that its a lot easier to make those design mistakes whwn using microservices. Like you said there is no tool to easly spot and fix those issues. In case of a monolith there are such tools and often resolve to simply view dependency graph in your IDE.
Re:IT Runs on Java 8 by hn_throwaway_99 on Saturday May 11, 2019 @07:35PM (#19889071)
I have never seen a microservices architecture where transactions spanning services were trivial.
Re:IT Runs on Java 8 by jayd16 on Sunday May 12, 2019 @04:12AM (#19890774)
If you need to do that then you've most likely cut along the wrong service boundry. Same thing can happen in a monolith, although you can kludge something out with spaghetti code I suppose. Doing it the right way in both cases takes about the same amount of work.
Re:IT Runs on Java 8 by he0001 on Sunday May 12, 2019 @02:31PM (#19893591)
How do you cut your service boundaries?