Top products from r/softwarearchitecture
We found 13 product mentions on r/softwarearchitecture. We ranked the 10 resulting products by number of redditors who mentioned them. Here are the top 20.
2. Clean Architecture: A Craftsman's Guide to Software Structure and Design (Robert C. Martin Series)
Sentiment score: 1
Number of reviews: 1
3. Design Patterns: Elements of Reusable Object-Oriented Software
Sentiment score: 2
Number of reviews: 1
Great product!
4. Domain-Driven Design: Tackling Complexity in the Heart of Software
Sentiment score: 2
Number of reviews: 1
5. Lean Software Development: An Agile Toolkit
Sentiment score: 1
Number of reviews: 1
6. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler))
Sentiment score: 1
Number of reviews: 1
Addison-Wesley Professional
7. Implementing Domain-Driven Design
Sentiment score: 0
Number of reviews: 1
Addison-Wesley Professional
8. Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems
Sentiment score: 0
Number of reviews: 1
My blog about software architecture: http://www.tutisani.com/software-architecture/ (may not be for very beginners but I hope that it's able to communicate important topics).
I'd also suggest reading the classic book about design patterns (a.k.a. Gang of Four): https://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612/ref=sr_1_3?crid=1XRJO0L09LHLY&keywords=design+patterns+elements+of+reusable+object+oriented+software&qid=1557502967&s=gateway&sprefix=design+patterns%2Caps%2C162&sr=8-3
There are several good thought leaders in this direction, specifically Martin Fowler (https://martinfowler.com/) and Eric Evans (he does not write much online, but his book is great - all about modeling properly): https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215
​
I'm big on modeling, objects, etc. so reply back if any questions.
>How do you all approach designing a solution like this assuming you will not be able to acquire an existing application?
I'll ignore the whole DB selection thing, because this is the real question that you need answered (and will eliminate the need for the DB thing)
My approach would be: focus on solving the clients problem as fast and cheap as possible. Some principles to follow:
I basically just described to you - in a super simplified way - the agile/lean way of building software.
>I am willing to put in the time and effort to learn what I need to learn here -- I just need some guidance!
Here are some book recommendations:
Lean Software Development: An Agile Toolkit
Clean Architecture
Continuous Delivery
I hope it helps. Feel free to reach out to me if you want to discuss this further.
A good place to start might be books like domain driven design distilled. https://www.amazon.com/Domain-Driven-Design-Distilled-Vaughn-Vernon/dp/0134434420
I've also found O Reilly's building microservice to be a decent primer. http://shop.oreilly.com/product/0636920033158.do
For server less, Martin Fowler is always a good place to start: https://www.martinfowler.com/articles/serverless.html
This one has some good info:
https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321
And prob this:
http://erlang.org/download/armstrong_thesis_2003.pdf
I also recommend his book: "SOA Patterns"
(http://www.amazon.com/SOA-Patterns-Arnon-Rotem-Gal-Oz/dp/1933988266).
This book will let you dive into soa architecture for architect point of view.
enterprise architecture as strategy (ross, well, robertson)
https://www.amazon.com/Enterprise-Architecture-Strategy-Foundation-Execution/dp/1591398398
No, no, no. The principle is great, but that book is bonkers.
You want the Vaughn books if you're doing DDD:
The bigger book: https://www.amazon.co.uk/dp/0321834577/ref=pd_lpo_sbs_dp_ss_1?pf_rd_p=569136327&pf_rd_s=lpo-top-stripe&pf_rd_t=201&pf_rd_i=0321125215&pf_rd_m=A3P5ROKL5A1OLE&pf_rd_r=83Y7X80HPERQ5AMCEXGG
The shorter book: https://www.amazon.co.uk/Domain-Driven-Design-Distilled-Vaughn-Vernon/dp/0134434420/ref=pd_sim_14_2?_encoding=UTF8&psc=1&refRID=M5QXQ063YDX0E768HE3S
Source: read all of them tried getting traction across multiple teams citing them as sources, and the Evans book is almost intractable to most. Vaughn also at least starts talking about CQRS in a reasonable way, and introduces it using DDD.