DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Software Design and Architecture
  3. Microservices
  4. Looking for Perfect Software Architecture? That May Take a Long Time.

Looking for Perfect Software Architecture? That May Take a Long Time.

Benjamin Laffont user avatar by
Benjamin Laffont
·
Aug. 06, 12 · Interview
Like (0)
Save
Tweet
Share
2.86K Views

Join the DZone community and get the full member experience.

Join For Free

low cohesion, modularity, dependency inversion, responsibility, interface segregation, overengineering, stovepipe syndrome, silver bullet or shotgun surgery—all of these techniques may lead you to the best solution, but the mirror edge is quite thin. at one extreme you will provide an architectural marvel that is maybe useless. on the other hand, you may create a genie in a bottle. this article will try to draw some typical situations of the real development world. we can symbolize a software feature by a circle and, in a normal production flow, a line that drives to a new feature. this line length represents the cost to produce a new feature.

let’s think of how we can represent a set of features in our day-to-day projects.

low extensibility

this pattern is typical to a little architecture that orchestrates too many features. it might be “perfect” if you were not in the middle of your project.

extensibility failure

think about a great architecture that allows pretty much everything. you may fail on one point that screws up everything. see the example below:

you have a perfect modular system, with an interface segregation and an injection system that allows you to supply services when you see “new concrete();” directly in the module code :)

too much extensibility

one of the most common mistakes is to oversize architecture. let's say your boss asked you to create one feature with four satellite features. why create a gas plant? this frequent over-engineering is due to our big egos :)

why "extensibility"?

someone asks you to create two features, one aggregating the other. it is a short-term project for short-term usage. the question is why use extensibility? you exceed delay, money, maintenance tasks, and many other metrics that can deprive you of your year’s allowance.

blank architecture

you may see a fully functional and complex architecture that ultimately goes unused. maybe your first plan was to embed two features and one was suppressed. maybe the developer took delight in creating a nice architecture. we can also speak about "anchor" that stays in the code without reason  except politic or "just in case."

copy paste

once pipes are created, you might want to do a quick job by copying and pasting and adapting it a bit. you may fall in an anti-pattern methodology error. you multiply pipes and multiply possible maintenance. why not factorize?

you might read:

http://en.wikipedia.org/wiki/yo-yo_problem

http://en.wikipedia.org/wiki/anti-pattern

original post:

http://www.alphablog.org/2012/08/04/perfect-software-arcitecture-does-not-exists/

Architecture Software

Published at DZone with permission of Benjamin Laffont. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Why You Should Automate Code Reviews
  • Streamlining Your Workflow With the Jenkins HTTP Request Plugin: A Guide to Replacing CURL in Scripts
  • Agile Scrum and the New Way of Work in 2023
  • How To Get Page Source in Selenium Using Python

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: