Book Image

Cracking the IT Architect Interview

By : Sameer Paradkar
Book Image

Cracking the IT Architect Interview

By: Sameer Paradkar

Overview of this book

An architect attends multiple interviews for jobs or projects during the course of his or her career. This book is an interview resource created for designers, consultants, technical, solution, domain, enterprise, and chief architects to help them perform well in interview discussions and launch a successful career. The book begins by providing descriptions of architecture skills and competencies that cover the 12 key domains, including 350+ questions relating to these domains. The goal of this book is to cover all the core architectural domains. From an architect’s perspective, it is impossible to revise or learn about all these key areas without a good reference guide – this book is the solution. It shares experiences, learning, insights, and proven methodologies that will benefit practitioners, SMEs, and aspirants in the long run. This book will help you tackle the NFR domain, which is a key aspect pertaining to architecting applications. It typically takes years to understand the core concepts, fundamentals, patterns, and principles related to architecture and designs. This book is a goldmine for the typical questions asked during an interview and will help prepare you for success!
Table of Contents (14 chapters)

Application architecture

In information systems, application architecture is one of several architecture domains that form the pillars of an EA or solution architecture. The term "application architecture" is commonly used for the internal structure of an application, for its software modularization. Application architecture is the methodology for ensuring that the applications suite being leveraged by the enterprise to create the composite architecture is reliable, scalable, and manageable.

What is the methodology for developing application architecture ?

The recommended methodology for developing application architectures is as follows:

  • Understand the applications landscape, the basis the application baseline, including business requirements, and it's correlation to business architecture

  • Identify logical applications and the best-fit physical components of applications

  • Define KPIs for the entire landscape by co-relating applications to services, functions, data, and processes

  • Elaborate application...