Quotessence
Home / Quotes / Quote by Nickolay Tsvetinov

Quote by Nickolay Tsvetinov

“If the application is event-driven, it can be decoupled into multiple self-contained components. This helps us become more scalable, because we can always add new components or remove old ones without stopping or breaking the system. If errors and failures are passed to the right component, which can handle them as notifications, the application can become more fault-tolerant or resilient. So if we build our system to be event-driven, we can more easily achieve scalability and failure tolerance, and a scalable, decoupled, and error-proof application is fast and responsive to users.”

Quote by Nickolay Tsvetinov

Book:Learning Reactive Programming with Java 8
Create image

Work

Learning Reactive Programming with Java 8

Browse quotes and source details for this work. more

Author

Nickolay Tsvetinov

Browse famous quotes and profile details for Nickolay Tsvetinov. more

You May Also Like

“Evolving a widely reused resource also requires coordination because changes must be compatible with all existing systems or users. Such coordination can slow down innovation... Some digital companies have even begun to explicitly favor duplication because their business environment rewards economies of speed.”

Software EngineeringSoftware Architecture
Book:The Software Architect Elevator: Redefining the Architect's Role in the Digital Enterprise
Create image

“Even if the ecosystem doesn’t change, what about the gradual erosion of architectural characteristics that occurs? Architects design architectures, but then expose them to the messy real world of implementing things atop the architecture. How can architects protect the important parts they have defined?”

Software EngineeringSoftware Architecture
Book:Building Evolutionary Architectures: Support Constant Change
Create image

“All too often architects make a decision that is the correct decision at the time but becomes a bad decision over time because of changing conditions like dynamic equilibrium. For example, architects design a system as a desktop application, yet the industry herds them toward a web application as users’ habits change. The original decision wasn’t incorrect, but the ecosystem shifted in unexpected ways.”

Software Architecture
Book:Building Evolutionary Architectures: Support Constant Change
Create image

“The other new role that evolutionary architecture creates has enterprise architects defining enterprise-wide fitness functions. Enterprise architects are typically responsible for enterprise-wide nonfunctional requirements, such as scalability and security. Many organizations lack the ability to automatically assess how well projects perform individually and in aggregate for these characteristics. Once projects adopt fitness functions to protect parts of their architecture, enterprise architects can utilize the same mechanism to verify that enterprise-wide characteristics remain intact.”

Software Architecture
Book:Building Evolutionary Architectures: Support Constant Change
Create image

“Metrics are a common adjunct to the deployment pipeline in incremental change environments. If teams use this effort as a proof-of-concept, developers should gather appropriate metrics for both before and after scenarios. Gathering concrete data is the best way to for developers to vet the approach; remember the adage that demonstration defeats discussion.”

Software Architecture
Book:Building Evolutionary Architectures: Support Constant Change
Create image