Highlights
- Don’t solve problems you don’t have
- It’s a simple question - what problem are you solving? Is it scale? How do you know how to break it all up for scale and performance? Do you have enough data to show what needs to be a separate service and why?
- Trying to shove a distributed topology into your company’s structure is a noble effort, but it almost always backfires.
- It’s a common approach to break up a problem into smaller pieces and then solve those one by one.
- So, the thinking goes, if you break up one service into multiple ones, everything becomes easier, right?
- The theory is sweet and elegant - each microservice is being maintained rigorously by a dedicated team, walled off behind a beautiful, backward-compatible, versioned API.
- In order to win the race, we don’t build one good race car - we build a fleet of shitty golf carts.
- Ultimately, when faced with the need to travel from New York to Philadelphia, you have two options.
- You can either attempt to construct a highly intricate spaceship for an orbital descent to your destination, or you can simply purchase an Amtrak train ticket for a 90-minute ride. That is the problem at hand.