D-Tier Development

Coining a buzzword (if it hasn’t been coined already), n-tier development is in the past.  D-Tier development is where we’re moving to.  The “D” can mean either “distributed” or, more in line with what I’m thinking, the ‘d’ in the word “multidimensional”, or simply “Dimensional.”

Why?  Because in an n-tier system, we still think of it fairly linearly: back-end, middle tier, and client-side, as one example.  OK, each tier may be implemented on a physically separate system, but doesn’t need to be.

A D-Tier implementation consists of autonomous entities distributed across a variety of physical and virtual platforms and interconnected in multidimensional ways.

Another aspect of D-Tier development is the highly “dynamic” nature of a distributed, autonomous entity architecture.  Entities can come and go, providing a continually changing environment of behavior that is tailored to the user’s needs.

  • Distrubuted
  • Dimensional
  • Dynamic

Start rethinking your application development in the D-Tier paradigm.

One thought on “D-Tier Development

  1. In your mind would this approach be somewhere between DDD and a micro service architecture?

    I’d be interested to see an example representation of the type of architecture you are discussing here

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s