Quotes About Decoupling

Another problem with service-level decoupling is that it is expensive, both in development time and in system resources. Dealing with service boundaries where none are needed is a waste of effort, memory, and cycles. And, yes, I know that the last two are cheap—but the first is not.

This means that the UI and the database can be plugins to the business rules. It means that the source code of the business rules never mentions the UI or the database.

The source code of higher-level services must not contain any specific physical knowledge (e.g., a URI) of any lower-level service.

A good architecture protects the majority of the source code from those changes. It leaves the decoupling mode open as an option so that large deployments can use one mode, whereas small deployments can use another.

We are finally no longer critically relevant to the world economy. The rest of the globe is strong enough to decouple from us. We, our country, our city, our infrastructure, are in a state of freefall.

let the Dow Jones plunge and markets all over the world also plummet. Some economists have advocated the decoupling of economies, but the crash in global markets, preceded by the financial crisis in the United States, is a stark reminder of the inter-dependence of the nations of the world, increasing ever since the first true decoupling occurred when God scattered the residents of the original Babylon and formed the nations.

A document shouldn't try to do what the code already does well.

It's important to note, however, that the decoupling required would not be a one-off phase: if GDP were to keep on growing, then the rate of decoupling would have to more than keep pace with it, year on year on year.

They start making a list: Every developer uses a common build environment. Every developer is supported by a continuous build and integration system. Everyone can run their code in production-like environments. Automated test suites are built to replace manual testing, liberating QA people to do higher value work. Architecture is decoupled to liberate feature teams, so developers can deliver value independently. All the data that teams need is put in easily consumed APIs

That means thinking about power differently. It means decoupling it from public prestige. It means thinking collaboratively, about the power of followers not just of leaders. It means, above all, thinking about power as an attribute or even a verb ('to power'), not as a possession.

The decoupling of power from size, and thus the decoupling of the capacity to use power effectively from the control of a large Weberian bureaucracy, is changing the world. And this decoupling invites a disquieting thought: if the future of power lies in disruption and interference, not management and consolidation, can we expect ever to know stability again?

The decoupling of power from size, and thus the decoupling of the capacity to use power effectively from the control of a large Weberian bureaucracy, is changing the world.