Donât solve problems you donât have (View Highlight)
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? (View Highlight)
Trying to shove a distributed topology into your companyâs structure is a noble effort, but it almost always backfires. (View Highlight)
Itâs a common approach to break up a problem into smaller pieces and then solve those one by one. (View Highlight)
So, the thinking goes, if you break up one service into multiple ones, everything becomes easier, right? (View Highlight)
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. (View Highlight)
In order to win the race, we donât build one good race car - we build a fleet of shitty golf carts. (View Highlight)
Ultimately, when faced with the need to travel from New York to Philadelphia, you have two options. (View Highlight)
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. (View Highlight)
(View Highlight)
(View Highlight)
(View Highlight)