Remember when they snuck off on some escape ship to go get help for their crew in imminent danger and then decided to dick around on some horse racing casino planet? It's like they completely forgot why they were there. I thought TLJ had some neat ideas but I don't know how anyone can overlook that weird loss of urgency in the middle of the film. It's like your house is on fire and your family is trapped upstairs, so you run over to a neighbor's house to call the fire department, but you discover that they got some dog fighting thing going on in the backyard so you decide to go deal with that first, then you call the fire department but it turns out the dispatcher was in cahoots with the arsonist who started it in the first place, and then you return home with your tail between your legs and your mom didn't even know you had left. The whole second act could have been a dream sequence and it wouldn't have changed a thing.
- Posts
- 1
- Comments
- 22
- Joined
- 3 yr. ago
- Posts
- 1
- Comments
- 22
- Joined
- 3 yr. ago
From my perspective the corporate obsession with microservices is a natural evolution from their ongoing obsession with Agile. One of the biggest consequences of Agile adoption I've seen has been the expectation of working prototypes within the first few months of development, even for large projects. For architects this could mean honing in on solutions in weeks that we would have had months to settle on in the past. Microservices are attractive in this context because they buy us flexibility without holding up development. Once we've identified the services that we'll need, we can get scrum teams off and running on those services while working alongside them to figure out how they all fit together. Few other architectures give us that kind of flexibility.
All this is to say that if your current silver bullet introduces a unique set of problems, you shouldn't be surprised if the solutions to those problems start to also look like silver bullets.