I’ve decided to take a break from some lower level stuff – server side languages, scripts and front end stuff. As in “break” – I meant in my blog posts. My thirst for more Javascript and PHP is unending so that is still quite active.<\/p> \r\n\r\n
I’ve developed a sudden interest in system architecture – I think this was ignited off a job requirement I’ve recently run across. Almost everything listed as a requirement I had covered and even the ones I wasn’t quite savvy with I knew I could pick up pretty fast – ie frameworks and libraries. When I look at job requirements, I look at the underlying fundamentals or lack thereof with regards to my toolbelt.<\/p> \r\n\r\n\r\n\r\n
I like realistic job requirements – they poke holes in me that need my attention. To my surprise – there was one requirement, well not exactly a requirement but “a plus” that humbled me. This was the concept of “System Architecture”.<\/p>\r\n\r\n
System Architecture<\/strong>. Yes I’ve covered this subject many times in the past, however this is something I should know, and know very well. Of my 15+ years as a software developer this is embarrassing. And so here I am, attempting to fill in the gaps. Because well, isn’t that what immersing yourself is all about?<\/p>\r\n\r\n System Architecture itself is so high level though, let’s get a bit more specific here since were talking about software. We are really talking about Software Architecture and Design.<\/p> \r\n\r\n So let’s get started with some concepts – Architectural vs Design, with an emphasis in architectural.<\/p> \r\n\r\n – High level universal scope – Also known as the N-tier Pattern1. Architectural Pattern<\/h2>\r\n
\r\n– How components are organized and assembled<\/p>\r\n\r\nArchitectural Pattern can be abstracted into two levels:\r\n\r\nLevel 1 – Monolithic, Level 2 – Layered<\/h3>\r\n
\r\n– Monolithic
\r\n– Separation of concerns
\r\n– Layers as major components<\/p>\r\n\r\n