Veresk Software Architecture


I suspect you have never had a chance to visit the Veresk Bridge. That’s cool. Neither have I. But humor me please and take a peek at it here.

Here is a slightly better-than-Wikipedia picture of the bridge:

veresk_bridge_3

I am going to tell you about the part that my mom told me when I was a kid and it’s a story that likely most Iranians-by-origin know as well, though its authenticity is still somewhat questionable.

The story goes that as the chief engineer, Mr. Walter Aigner, finished the architecture work and once the bridge construction was fully ready to be “tested”, he called upon Reza Shah (the head monarch of Iran at the time) to come visit the beauty in all its glory. He did also request that Reza Shah must have the honor of boarding the very first train ever to cross the bridge and cut the metaphorical ribbon with wheels on burning coal.

The bridge was a very big deal at the time; a symbol of magnificence, pride and glory for the nation. The opportunity for the common folk to see their Shah up close and witness him take part in the community to “ride the train along with his countrymen” was going to be both advantageous to the administration and a note of joy and amusement for the people.

So of course, he obliged. I also suspect that Reza Shah was not a big fan of testing things in production either. But he did ask that Mr. Aigner along with the rest of his family stand underneath the bridge and watch as he, aboard the train, crossed over. Remember; this was a first test. A smoke test that could have literally ended in smokes.

Mr. Aigner was of course so confident in his design and implementation of the bridge that he accepted. His family patiently watched from 100 meters below while the train successfully crossed the bridge without any accidents. “Cheers to the Shah”, people must have yelled.

So why am I telling you about all this? Because that’s exactly how I feel about software architecture and the responsibility of architects as they pass through iterations of design and implementation.

If you are not willing to stand by your design and your ideas in confidence…if you are not able to execute in action what may only seem a pretty diagram on paper…if you are not willing to get hands-on and learn the nuances of implementing said ideas and weigh pros and cons of each in practice…none of that is of any use to anybody, really.

Of course, let’s clarify that I:

  • Have nothing against bridges, trains or crossing over things.
  • Am not advocating for any sort of monarchy.
  • Am not advocating for any kind of violence and hostility during software design.
  • Am not advocating that you should gather your folks and sprawl out underneath the data center as you press the power button on your Pentium II.
  • Seriously shall question your sanity if you go to production with Pentium IIs.

All I am saying is, you should be held accountable. That’s all.

Misagh Moayyed

PS: The Chief Engineer, Austrian Walter Aigner, following his wishes, is today buried in the local cemetery of Veresk. 

Related Posts

CAS 6.0.0 RC3 Feature Release

...in which I present an overview of CAS 6.0.0 RC3 release.

Apereo CAS - Multifactor Authentication with RADIUS

Learn how Apereo CAS may be configured to trigger multifactor authentication using a RADIUS server and its support for the Access-Challenge response type.

CAS Vulnerability Disclosure

Disclosure of a security issue with the MFA features.

CAS 6.0.0 RC2 Feature Release

...in which I present an overview of CAS 6.0.0 RC2 release.

Apereo CAS - dotCMS SAML2 Integration

Learn how to integrate dotCMS, a Content Management System and Headless CMS, with Apereo CAS running as a SAML2 identity provider.

Effective Software Troubleshooting Tactics

A collection of what hopefully are obvious troubleshooting tactics when it comes to diagnosing software deployment issues and configuration problems.

Apereo CAS - MaxMind Geo2IP ISP Integration

Learn how you may determine the Internet Service Provider, organization name, and autonomous system organization and number associated with the user's IP address in CAS using MaxMind services and present warnings in the authentication flow for the end-user if an IP address is matched.

Notes from Better by Design 2018

Be interested in humans and human success.

Apereo CAS - Authentication Lifecycle Phases

Tap into the Apereo CAS authentication engine from outside, and design extensions that prevent an unsuccessful authentication attempt or warn the user after-the-fact based on specific policies of your choosing.

CAS 6.0.0 RC1 Feature Release

...in which I present an overview of CAS 6.0.0 RC1 release.