concept functionality in category spring

appears as: functionalities, functionality, functionality, functionalities
Spring Security in Action

This is an excerpt from Manning's book Spring Security in Action.

Generally, as developers, we start by learning that the purpose of an application is to solve business cases. This purpose refers to something where data could be processed somehow, persisted, and eventually displayed to the user in a specific way as specified by some requirements. This overview of software development, which is somehow imposed from the early ages of learning development, has the unfortunate disadvantage of hiding practices that are also part of the process. While the application works correctly from the user’s perspective, and in the end, it does what the user expects in terms of functionalities, there are lots of aspects hidden in the final result.

When we implement apps, we use two fashions of implementing the functionalities:

  • Imperative - your application processes a bulk of data all at once. For example, a client application calls an endpoint exposed by the server and sends all the data that needs to be processed to the backend side. Say you implement a functionality where the user uploads files. If the user selects a number of files, and all of them are received by the backend application all at once to be processed - you’re working with an imperative approach.