Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The End of Microservices

lightstep.com

Post reply on HN
Print view View original

1–10 of 154 posts

Re: The End of Microservices

#3

Post by msoad »

One thing I don't like about SOA is that an error does not have a full stack trace. I know Zipkin exists but it's nowhere close to what we had in a monolithic app where you could just put a breakpoint and trace back to where exactly an error is thrown.

If we can find a way of running a giant monolithic app in development and production environment without vertically scaling our machines, I would rather have that.

Every bug I'm working on is like a mystery that I have to hop to many services to find what's going.

I also think HTTP is the worst protocol for apps to talk to each other.

Re: The End of Microservices

#4

Post by sinzone »

When this year I came back from Dockercon I immediately wanted to write something very similar to what this article describes. I wanted to imagine a world where Containers and Microservices were part of the past already, and so I wrote "DockerCon 2020" [1] and how it will look like.

[1] https://medium.com/@sinzone/dockercon-2020-a513ed04eefb#.rbz...

Re: The End of Microservices

#5

Post by malandrew »

msoad wrote: post #3

One thing I don't like about SOA is that an error does not have a full stack trace. I know Zipkin exists but it's nowhere close to what we had in a monolithic app where you could just put a breakpoint and trace back to where exactly an error is thrown. If we can find a way of running a giant monolithic app in development and production environment without vertically scaling our machines, I would rather have that. Eve…

http://opentracing.io/

Re: The End of Microservices

#6

Post by themihai »

msoad wrote: post #3

One thing I don't like about SOA is that an error does not have a full stack trace. I know Zipkin exists but it's nowhere close to what we had in a monolithic app where you could just put a breakpoint and trace back to where exactly an error is thrown. If we can find a way of running a giant monolithic app in development and production environment without vertically scaling our machines, I would rather have that. Eve…

Depending on your requirements micro-services may be a good or a bad solution. If the communication/protocol becomes too chatty that may be a sign you are doing it wrong.

Re: The End of Microservices

#7

Post by slowmovintarget »

malandrew wrote: post #5
msoad wrote: post #3

One thing I don't like about SOA is that an error does not have a full stack trace. I know Zipkin exists but it's nowhere close to what we had in a monolithic app where you could just put a breakpoint and trace back to where exactly an error is thrown. If we can find a way of running a giant monolithic app in development and production environment without vertically scaling our machines, I would rather have that. Eve…

http://opentracing.io/

I was thinking of a simpler "Y U no log?!?" with correlation IDs but this is much cooler.
Post reply on HN