Architecture design

One mistake many make while building architecture for any application / system is to build the architecture using best/latest technology in isolation.

Architecture design has to be mapped to the use case and requirements.

Areas listed below and more should be considered while making design for the architecture:
1. NFR (Non functional requirements)
2. Security
3. Groups/roles/etc.
4. Integration
5. Use case
6. Information processing, etc.

All of the above and more should be considered upfront and consideration should not just be given for the best/latest technologies. Unless for example we consider how many users will use the system, which type of information exists, what are it’s updation rates, etc. who will access the system with what rights, what scalability is needed, how fast will the system change, what are the uptime requirements, etc. we can’t build the right system.

All of the above should be covered right from design and appropriately data should be partitioned, security design should be built, scalability should be thought of and issues like groups/roles/users, identity and access management should be mapped to the use case or the requirement.

By Neil Harwani

Interested in movies, music, history, computer science, software, engineering and technology

Leave a comment