Your Platform Is a Matrix: How to Get From O(B × P) to O(B + P)
Some architecture problems look fine while the system is small.
A few businesses. A few payment methods. Each business wants slightly different accounting, so you wire each payment method to each business.
Nothing looks broken yet.
Then both sides grow.
A new payment method shows up and suddenly needs accounting logic for every business already on the platform. A new business launches and every existing payment method has to learn it.
That is not a platform. That is a matrix.
I hit this on payment accounting. The lesson was not really about payments.
When two parts of a platform grow on their own and still know too much about each other, integration cost multiplies. Another abstraction layer or a fatter shared API is usually the wrong fix. You need a boundary where neither side has to know the other exists.
When system A knows which system B it...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
