#non-functional-requirements

Uses: 4

Latency budget as the tool to address latency requirements

Tags: #thoughts #non functional requirements #latency #internet #protocols #tcp/ip #dns #http #tls

Latency requirements determines the degree of user satisfaction about the web service. Software development practices shall consider the end-to-end latency as one of user-oriented characteristics during the entire life-cycle of an application. Latency budget defines latency target and non-functional requirements for distributed systems.

In-depth guide to sources of latency in distributed systems.

Tags: #thoughts #non functional requirements #latency #networking #mobile network #microservices #protocols #tcp/ip #http

Distributed systems involve various technologies and communication principles that bring overhead and latencies. The root cause of latencies varies from physical properties of the network to the quality of software components. The post discussed sources of latencies from the prism of infrastructure, protocol and application.

What is the user’s expectation about the latency of Internet Services?

Tags: #thoughts #non functional requirements #latency #networking #mobile network #consumer journey #user experience #microservices

End-to-end latency is one of user-oriented characteristics used for quality assessment of distributed software architecture. Research indicates that a service fails to meet user needs if a transaction cannot be accomplished within 3 - 4 seconds.

Migrate Your Application To Cloud Age

Tags: #architecture #microservices #non-functional requirements #scalability #consumer journey #search #domain driven design #common data model #distributed system #cloud

Microservices became a design style to implement applications in the cloud. It define system architectures, purify core business concepts, evolve solutions in parallel.