Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Aspiring Solution Architects   (RSS)
Sorry, but there are no more tags available to filter with.

Agility: Automation for Better Outcomes and Feedback

A bad habit of several developers has to do with entering in a long tunnel of coding for an application project, relegating a more or less acceptable executable for the last project stages. That has several risks: Feedback from users and customers delayed,

From Classes To Components

In n-tier, distributed applications, we have to decide which logic deploy where. Those deployments are all about installing components in specific places but, what are components exactly? What distinguishes a component with respect of a mere class? Actually,

Software Architecture: Past, Present and Future

What is exactly software architecture? Do we really need it? Why have we only recently been discussing it? Is there suddenly a contagious fever about software architecture infecting those who claim to be architects? Who are they actually: gurus, just

Architecture Best Practices

In "Last Call To Design Patterns" we described design patterns as "reusable solutions for frequent problems". It's all about thoughtful approaches to avoid common pitfalls And, actually, Patterns are just one of a set of disciplines which help us to achieve

Passing Data Between Layers and/or Tiers

While we were commenting some high-level strategies for data-access in a previous article , we mentioned a popular pattern used to interchange information between layers or tiers . We are talking about the Data Transfer Object (DTO) pattern . As the MS

Data Access Strategies

We have seen in the post about 3-Layer architectures , that the Data Access Layer isn't the persistence repository, but a set of strategies for accessing it The challenge you as an architect have to face when designing this layer is multiple: How much

3-Tier, 3-Layer, MVC: a Trio of Famous Trios

Contemporary applications are being based on three popular architectural approaches. They are 3-layered architecture 3-tier architecture Model-View-Controller architecture There exists certain degree of confusion between all the three approaches. Mostly

Layered Applications: Let's Talk About Business

I remember a time when applications were just end to end programs, collections of lines of code with no distinction between presentation, domain logic and data access. Such kind of applications is remembered as spaghetti code Fortunately nowadays enterprise

Aims and Means of Asymmetric Cryptography

Usually we tend to center the concept of Authentication to mere users, through and exhibited password as a credential But beyond the user, how to be sure about authenticity of other assets ? For example, how can we be sure about, once the user is authenticated,

How Sure Are You About Security?

Even though it´s surprising, an important number of architects don't worry enough about security aspects Talking with some of them, they considered that Security is a topic so complex -they are right in this appreciation- that developers don't have to

An Old Antipattern: "Too Much Architecture"

At least in Software Engineering, but I guess the same applies to other sciences, there are ideas, concepts and paradigms easy to understand, but not so easy to implement in practice I remember, for instance, I understood very quickly OOP. It was pretty

Fighting Against Coupling: a Moment for Reflection

One of the most recurrent problems we have to face, as aspiring architects, is the problem of dealing with highly adaptable applications for different environments For instance, we need to build an application able to access a DB/2 database in one environment,

Two-Phase Commit (2PC): Coordinating Transactions in Distributed Environments

There was a time when applications were isolated as a common issue, and having each one just one repository was usual Sometimes, we needed to update diverse records to the repository, let's say a purchase order header with its purchased items. Those times,

Starting with Model/View/Controller (MVC) Architecture Pattern

With the massive advent of Internet, mobility and other network technologies, distributed programming is more popular than ever and it's unimaginable the idea that stand alone applications can come back They are gone So immediately a coupling crisis appeared

Last Call to Design Patterns

When planing the architecture of an application, the architect has a powerful set of tools available: Design Patterns Design Patterns are reusable solutions for frequent problems, upon different contexts. The more you know about them, the more self-confidence
More Posts Next page »
 
Page view tracker