Forgot to add under non-functional requirements under heading
- *Supportability and Maintainability*
Someone queried the other day on how to shutdown a streaming job
gracefully, meaning wait until such time as the "current queue" including
backlog is drained and all processing is completed.
Hello Mich
Thank you for your great explanation.
Best
A.
On Tuesday, 27 April 2021, 11:25:19 BST, Mich Talebzadeh
wrote:
Hi,
Any design (in whatever framework) needs to consider both Functional and
non-functional requirements. Functional requirements are those which are
related to
Hi,
Any design (in whatever framework) needs to consider both Functional and
non-functional requirements. Functional requirements are those which are
related to the technical functionality of the system that we cover daily in
this forum. The non-functional requirement is a requirement that
Hello,
When we design a typical spark streaming process, the focus is to get
functional requirements.
However, I have been asked to provide non-functional requirements as well.
Likely things I can consider are Fault tolerance and Reliability (component
failures). Are there a standard list of
