nick_tune, to random
@nick_tune@hachyderm.io avatar

What do I think was missing from the book Architecture Modernization? Great question from @eduardodasilva yesterday as part of an interview that will be published soon.

While designing a great architecture, prioritizing areas with the most business impact, and having an effective migration plan are essential to get right, so are all of the small things that happen on a day to day basis.

1/3

nick_tune,
@nick_tune@hachyderm.io avatar

This is covered in the book, notably the chapter on AMETs. But it's a great topic that I would love to have covered in much more detail - delivery management, change management, leadership etc. in the context of architecture modernization.

It will probably be the focus of future blog posts and talks (I'm definitely not writing any new books). I appreciate any recommendations for existing resources on the topic

https://esilva.net/articles/architecture-modernization-enabling-team

3/3

nick_tune, to random
@nick_tune@hachyderm.io avatar

One of the most fascinating things about software architecture is how choices in the past can have such a strong influence on the system for years to come.

You might make a decision that seems trivial at the time, but new features get layered on top of your design's assumptions.

These bakediin constraints limit how you can evolve the system,...

1/2

nick_tune, to random
@nick_tune@hachyderm.io avatar

When migrating incrementally to a new architecture, and the new and old will run in parallel, in what order should you migrate?

  • reads first
  • writes first
  • by use case (containing reads and writes)

This is a question that always comes up during modernization and I've been enjoying some great discussions about this at PayFit.

There are too many pros and cons to say any option is the best. It depends on what you want to optimize for.*

1/2

nick_tune, to random
@nick_tune@hachyderm.io avatar

Should you start an architecture modernization journey by building something completely new outside of your existing systems?

This can be effective as a way of demonstrating what's possible in your proposed "new world".

Faster time-to-market, better reliability, improved compliance, more efficient delivery etc.

1/n

nick_tune, to random
@nick_tune@hachyderm.io avatar

Just noticed that there is now audio book version of architecture modernization available.

You can listen to the first chapter for free. It's 28 minutes at default speed.

https://www.manning.com/books/architecture-modernization

nick_tune, to random
@nick_tune@hachyderm.io avatar

I had a great time at NDC London this week.

I enjoyed facilitating a DDD workshop and doing a little talk about architecture modernization.

The slides for this and all of my talks are available on my site, along with videos where recorded (I’m not saying they're good, I'm just saying they are there).

https://nick-tune.me/speaking

nick_tune, to random
@nick_tune@hachyderm.io avatar

Would it ever make sense to have a team composed of 75% or even 100% external consultants/contractors on a modernization initiative?

Sometimes I do agree/advocate for this approach.

Mostly, I see it as a pattern for validating an approach and showing what is possible.

Ideally, it should be a short-term stepping stone to building in-house capability.

nick_tune, to random
@nick_tune@hachyderm.io avatar

Just published: Forming an Architecture Modernization Enabling Team (AMET)

This was written in collaboration with @eduardodasilva and tries to convey some of our key learnings in 2023.

Always happy to receive feedback on this article or suggestions for other topics that we need to cover.

https://medium.com/nick-tune-tech-strategy-blog/forming-an-architecture-modernization-enabling-team-amet-50d70a789331

nick_tune, to random
@nick_tune@hachyderm.io avatar

After 3+ years in the making I am now the happy owner of physical copies of my book Architecture Modernization.

It's not really fair to call it "my" book because much of the content is real world stories provided by industry experts, so I would like to share this moment with all of the contributors:

cont’d….

nick_tune, to random
@nick_tune@hachyderm.io avatar

One of the most enjoyable aspects of writing my book architecture modernization was working with industry experts to write case studies.

It's something I want to continue. I'm going to set up a website for modernization info with a section dedicated to case studies.

If you'd like to share a modernization case study (or if you're just curious) then please contact me directly. I'll work with you closely at each step to create a polished article.

nick_tune, to random
@nick_tune@hachyderm.io avatar

Should you create a separate team to work on modernizing the legacy monolith while other teams focus on building new features outside the legacy?

This is a topic I've discussed on multiple occasions recently, and it's not an uncommon modernization question in general.

I'm generally cautious of this approach because...

1/n

nick_tune, to random
@nick_tune@hachyderm.io avatar

Quick update on my book:

4 out of 17 chapters have passed through copy editing. Target is for all 17 to be completed this month.

AFAIK, we are still on schedule for physical copies to be available this year, possibly 31st October.

Thanks for all of your support. This is a tiring process and every bit of help gives me a tiny extra bit of motivation.

https://www.manning.com/books/architecture-modernization?new=true&experiment=B

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • GTA5RPClips
  • DreamBathrooms
  • everett
  • magazineikmin
  • Durango
  • InstantRegret
  • Youngstown
  • mdbf
  • slotface
  • rosin
  • thenastyranch
  • kavyap
  • ethstaker
  • megavids
  • tacticalgear
  • cubers
  • cisconetworking
  • osvaldo12
  • khanakhh
  • ngwrru68w68
  • modclub
  • tester
  • anitta
  • normalnudes
  • Leos
  • provamag3
  • lostlight
  • All magazines