4 ms·

Disaster #1 is too small services, and Disaster #4 is huge, shared databases (between many services). Which reaffirms my overall opinion that most people writi

by slver 5y ago

Disaster #1 is too small services, and Disaster #4 is huge, shared databases (between many services). Which reaffirms my overall opinion that most people writing services have no idea what's a service and what it encapsulates (it encapsulates its own state, for example, it's basically distributed OOP). BTW, remember when "your service should be 100 lines of code top" was considered a best practice? Why is it so hard for most to resist this hype nonsense wave when its oncoming and it's so hard to resist the anti-hype wave that inevitably follows it? Because hype and anti-hype are simply the oscillation of a sea of empty minds in look for a solution to a problem they don't understand. I've been writing service oriented apps for decades. In my "world" nothing has changed.

unlimit 5y ago
> Why is it so hard for most to resist this hype nonsense wave when its oncoming and it's so hard to resist the anti-hype wave that inevitably follows it? Because then how will one do career development? We are building now for a client and the client wants it, I can feel it in my bones that what we are building is far more complex and will be difficult to maintain. I am no expert in microservices but this hunch is just coming from common sense.
- slver 5y ago
  In your situation it seems like a non-technical person in charge of technical decisions. Those decisions are by definition poor quality. But the really bad moment is when the developers themselves make those bad choices entirely on their own.
  - unlimit 5y ago
    > In your situation it seems like a non-technical person in charge of technical decisions. Those decisions are by definition poor quality. The client is to blame. The client let go of all the people who knew the technical side of the product and has hired an architect to re-architect everything. And the client is in a hurry.
jeffbee 5y ago
No, I don't remember when 100-line services were the "best practice" because I don't elevate every stupid idea that some inexperienced kid blogs about to "best practice". I know 1000s of people in the industry and exactly none who would agree that is a best practice. Successful large-scale systems are built around much larger services, like "deliver this e-mail message" or "store this blob of data".
- slver 5y ago
  You legit called 1000s of people in the industry to ask them what they think about the 100 lines meme. Great, appreciate your effort there. /s
yxhuvud 5y ago
I think one major contributing reason is that the amount of programmers is still rising so fast, with each new generation being larger than the previous. Then every generation see the tail end of the previous generation and will then rebel against it to solve the issues. That they will have moderated after a couple oscillations doesn't matter as there is so few of them in most work places.

by slver 5y ago

unlimit 5y ago

> Why is it so hard for most to resist this hype nonsense wave when its oncoming and it's so hard to resist the anti-hype wave that inevitably follows it? Because then how will one do career development? We are building now for a client and the client wants it, I can feel it in my bones that what we are building is far more complex and will be difficult to maintain. I am no expert in microservices but this hunch is just coming from common sense.

slver 5y ago
In your situation it seems like a non-technical person in charge of technical decisions. Those decisions are by definition poor quality. But the really bad moment is when the developers themselves make those bad choices entirely on their own.
- unlimit 5y ago
  > In your situation it seems like a non-technical person in charge of technical decisions. Those decisions are by definition poor quality. The client is to blame. The client let go of all the people who knew the technical side of the product and has hired an architect to re-architect everything. And the client is in a hurry.

jeffbee 5y ago

No, I don't remember when 100-line services were the "best practice" because I don't elevate every stupid idea that some inexperienced kid blogs about to "best practice". I know 1000s of people in the industry and exactly none who would agree that is a best practice. Successful large-scale systems are built around much larger services, like "deliver this e-mail message" or "store this blob of data".

slver 5y ago
You legit called 1000s of people in the industry to ask them what they think about the 100 lines meme. Great, appreciate your effort there. /s

yxhuvud 5y ago

I think one major contributing reason is that the amount of programmers is still rising so fast, with each new generation being larger than the previous. Then every generation see the tail end of the previous generation and will then rebel against it to solve the issues. That they will have moderated after a couple oscillations doesn't matter as there is so few of them in most work places.