article thumbnail

Thoughts on organizing architecture

Xebia

No need to negotiate the proposed solution for any given problem with the budget holder. No long debates with other engineers about the envisioned solution. The scope of a team often concerns a limited number of components, microservice or other functionalities. Great for our agility, but it also has consequences.

article thumbnail

Thoughts on organizing architecture

Xebia

No need to negotiate the proposed solution for any given problem with the budget holder. No long debates with other engineers about the envisioned solution. The scope of a team often concerns a limited number of components, microservice or other functionalities. Great for our agility, but it also has consequences.

article thumbnail

Grown-Up Lean

LeanEssays

Small, independent teams own a small service – called a microservice these days. Do not think of a microservice architecture as a flat layer of tiny services. Moving expenditures from capitalized to expensed not only changes whose budget the money comes from; it can have tax consequences as well. They obsess over customers.