From the course: Java EE: Design Patterns and Architecture

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Why do we need architecture?

Why do we need architecture?

From the course: Java EE: Design Patterns and Architecture

Start my 1-month free trial

Why do we need architecture?

- [Instructor] So why do we need enterprise architecture and why don't we just start coding and see how it goes? Well that approach is okay if you're just trying out a new idea or learning an unfamiliar API. But trying to build a large online banking application that's got to handle millions of transactions securely every hour and integrate with hundreds of back end legacy applications, you will soon run into problems. And you will soon run out of money as you solve problems and refactor your application. Architecture is a means of describing a complex end product. In terms of its constituent parts and how they fit together. And enterprise architecture is a solution to a problem already solved by developers and architects in the past. You don't have to solve the same problem twice. Using enterprise architecture to solve the problem of how to structure your application frees you to work on problems that don't have a known solution. Just as using Open Source software means you don't…

Contents