Looking for good software architecture resources!
from lascapi@jlai.lu to programming@programming.dev on 16 Mar 21:26
https://jlai.lu/post/34643152

Hi there, I’m looking for good software architecture resources: blog, wiki or community.

I know good enough the basis of OOP and ‘Design Pattern’ and I’m looking for something more advanced.

One of my goal is to create local first software but anything with network and web archi are welcome too. 🙂

#programming

threaded - newest

one_old_coder@piefed.social on 16 Mar 21:50 next collapse

There are a whole bunch of architecture books published by Oreilly that I have bought and plan to read. They were available for a few bucks in a previous Humble Bundle, and cover the topics:

  • Head First Software Architecture
  • Fundamentals of Software Architecture
  • Flow architectures
  • Domain-driven Design
  • Micro-services
  • Agile stuff
  • Scalable Systems
  • API Management
  • etc.

All are available on Anna’s Archive. I like the Head First book to have an overview of architecture.

human@slrpnk.net on 16 Mar 23:09 next collapse

I second this and would also recommend the Software Architecture Book Club podcast where the authors cover a chapter each episode (Head First Software Architecture and then Fundamentals of Software Architecture).

I would also recommend the InfoQ architecture RSS feed to stay current.

one_old_coder@piefed.social on 17 Mar 04:55 collapse

Amazing, thanks.

Edit: I never knew that InfoQ was a good resource. That’s a nice additional link.

HelloRoot@lemy.lol on 17 Mar 06:52 collapse

I recommend “Software Architect’s Handbook” by Joseph Ingeno as an intro/overview

mesamunefire@piefed.social on 16 Mar 23:28 next collapse

“Build APIs You Won’t Hate: Everyone and their dog wants an API, so you should probably learn how to build them "

Great book, if a bit dated on the coding examples. It goes over common issues with APIs that I have seen play out.

“Working Effectively with Legacy Code” - Excellent book that goes over what to do in plain english when you got stuck with legacy code.

Paragone@piefed.social on 17 Mar 03:29 collapse

This is a bit beyond architecture, but being competent to build a mathematically bug-free API is probably something that few programmers would even bother trying to compete-against..

https://leanpub.com/algebra-driven-design

I think there is a fundamental mis-framing, throughout the entire software/development understanding..

I think that the architecture needs to be simultaneously agilely-devloped, but into an executable-model, a kind of toy-implimentation, so it is easy to change the architecture, low-cost, BEFORE one converts it into load-bearing, & therefore unchangeable architecture ( architecture’s the hardest thing to change, as it’s most-fundamental )

So, I think that the proper way is to do it in 2 stages:

  1. agilely develop the architecture, until ALL required-kinds-of-function are working, in the toy-model, & one has re-architected it so that the structure is right, & then
  2. set about converting it from the high-level-language to whatever production-language it is that is efficiency-optimal, for production-scale.

This is part of an idea from years ago: I read in a Wiley GAAP book that I happened to be glancing into, that it’s a violation of GAAP to prototype any project in any language other than the final-implimentation-language, & expense that prototype.

Which is totally insane!

Prototype in the highest-level-language you can, to get the domain+architecture right, then reimpliment what you have to in the most production-efficient/effective language for that project.

GAAP ( of that year ) is categorically wrong: it penalizes optimal-prototyping.

It was years-later before I discovered that an English mathematician ( roundish ginger, worked in Glasgow, no idea what his name was, sorry ) had studied the difference between complex projects which worked vs ones which died, & it was the visual-spacial-representation-of-the-model, & the complete-coverage executable-model which made the successes win.

So, I just put those ideas together.

_ /\ _

MonkderVierte@lemmy.zip on 17 Mar 11:43 next collapse

Easy. Just leave the bad parts out.

locuester@lemmy.zip on 17 Mar 15:02 collapse

Martin Fowler’s “Patterns of Enterprise Application Architecture” really helped me understanding how to break things down. Pretty sure it’s still just as relevant today.