When we start building an application, we have a set of requirements, and we try to design a solution that we feel will fulfill all the requirements. This design is known as application architecture. One important factor to consider is that your architecture should not only take care of current requirement, but should also anticipate expected future changes and take them into consideration. Quite often, there are some unspecified requirements, known as non-functional requirements, that you need to take care of. Functional requirements will be given as part of the requirements document, but architects or senior developers are expected to figure out non-functional requirements themselves. Performance needs, scalability needs, security requirements, maintainability, enhanceability, availability of applications, and so on, are some of the important...
United States
Great Britain
India
Germany
France
Canada
Russia
Spain
Brazil
Australia
Singapore
Hungary
Ukraine
Luxembourg
Estonia
Lithuania
South Korea
Turkey
Switzerland
Colombia
Taiwan
Chile
Norway
Ecuador
Indonesia
New Zealand
Cyprus
Denmark
Finland
Poland
Malta
Czechia
Austria
Sweden
Italy
Egypt
Belgium
Portugal
Slovenia
Ireland
Romania
Greece
Argentina
Netherlands
Bulgaria
Latvia
South Africa
Malaysia
Japan
Slovakia
Philippines
Mexico
Thailand