Picture Wall - 118 pics
linpengcheng/PurefunctionPipelineDataflow: My Blog: The Grand Unified Programming Theory: The Pure Function Pipeline Data Flow with principle-based Warehouse/Workshop Model
If All You Have Is a Database, Everything Looks Like a Nail - Scattered Thoughts on Distributed Systems
sirupsen/napkin-math: Techniques and numbers for estimating system's performance from first-principles
Context Mapper | Context Mapper is an open source project providing a Domain-specific Language (DSL) based on Domain-driven Design (DDD) patterns for context mapping and service decomposition.
Architects Zoom In and Out, See Different Things (Thinking Like An Architect Part 5) - The Architect Elevator
[archiloque.net] “Les juniors aiment mettre en place des solutions, les seniors aiment résoudre des problèmes”
GitHub - lucasepe/draft: Generate High Level Microservice Architecture diagrams for GraphViz using simple YAML syntax.
GitHub - ddd-crew/ddd-starter-modelling-process: If you're new to DDD and not sure where to start, this process will guide you step-by-step
(3) BDX I/O 2019 - Test d’architecture avec ArchUnit : Mise en œuvre pour le DDD - Xavier Blanc - YouTube
1and1/c4-notation: Technical resources for using the C4 model for visualizing software architecture.
Nicolas Grilly sur Twitter : "Only 3 good reasons for using #microservices instead of building a monolith: - You have multiple teams with clear responsibilities: 1 service per team - You use various technologies: 1 service per tech (e.g. Go and JVM) - Your services scale differently (CPU, RAM, disk, network)"
Patrick McKenzie sur Twitter : ""Monoliths versus microservices: Make it a monolith. Done. You won't have sufficient organizational complexity to justify the engineering tax of microservices until you have multiple engineering teams, and plausibly your company never gets there.""
Software Architecture and System Design - Getting Your Grip and Some Related Resources | Tugberk Ugurlu @ the Heart of Software
John S Nolan sur Twitter : "My goodness there's a lot of nonsense talked about software architecture"
Tom Glover sur Twitter : "I hereby define my very first original architectural buzz phrase. I do believe it sums up all of our joint frustrations over the years. Any acronym resemblance to actual vendors, living or dead is purely coincidental . @tetradian @boicy @simonbrown #SteampunkArchitecture… https://t.co/ELJPHveUUB"
Grady Booch sur Twitter : "The best formal and unambiguous specification of a software-intensive system is its executable code. A specification that is, however, insufficient for visualizing, reasoning about, understanding, and communicating about that system."
Savvas Kλeanthous 🇬🇧🇪🇺🇨🇾 sur Twitter : "When messages are transmitted they should include at minimum: 1. Message name 2. Name of service which owns the contract of the message 3. Message version 4. Message unique id 5. Correlation id 6. Causation id 7. UTC Timestamp [1 of 5"
Mario Fusco 🇪🇺 sur Twitter : "Applying the KISS principle also implies doing "boring" stuff instead of blindly following the coolest trends of the moment. Do monoliths unless you don't need microservices for a good reason. Use synchronous code unless you don't need async or reactive for a good reason.… https://t.co/qL0G3wgcmp"
Franck Pachot sur Twitter : "So, today, #monolithic is used as a pejorative word for software which: - link their functions to be executed by one processor without unpredictable latency - are clever enough to share memory among multiple processes - can read/write to same files from multiple nodes 🙄"
VisArch sur Twitter : "We let modeling fall out of practice. We need to use UML, or UMLish, or C4 plus UMLish, and/or ad hoc sketches. Get ideas out of our heads where we can see what we’re thinking..."
Sonia Gupta sur Twitter : "Sometimes I think microservices architecture is just an excuse for developers to build a lot of unnecessary shit. Something tech is really good at doing."
Darren Shepherd sur Twitter : "Microservices are a way to ensure your application has the same level of complexity as your organization."
thepracticaldeveloper/practical-architecture: A set of resources to become a Practical Software Architect: decision making, efficient meetings, architecture guide, etc.
Mike Kerr on Twitter: "I need to absorb and map out a large complex legacy system as the main lead of our team transitions to another team. I need to capture DB Tables, APIs, Business Logic and present to my Director in a few weeks. What is the best way/tool to organize all that?"
Lorin Hochstein on Twitter: "I’m a big believer in the following two statements: 1. You should design your system so that you never need to ssh to prod to debug an issue. 2. You should never prevent engineers from being able to ssh to prod to debug an issue.… https://t.co/kwmiyH0SXN"
Andrew Clay Shafer 雷启理 on Twitter: "most people are creating unmitigated horrors with microservices in nearly exactly the same way and for nearly exactly the same reasons they created disasters with Object Oriented Programming, the previous software panacea"
Matt Stine on Twitter: "had another opportunity to do an architecture review for a monolith to microservices migration today...observations to come:"
Peter Storch on Twitter: "It started with standardizing boxes and arrows and grew up to a nearly executable complex thingy. I think it is still useful to communicate some ideas, as long as you don't try to generate something out of it. But now everyone draws boxes and arrows differently again.… https://t.co/nPahLgSQmC"
docToolchain/docToolchain: a Gradle based AsciiDoc Toolchain for Software Architecture Documentation
Luis Fraile on Twitter: "Interesting things you find in friend’s offices #DevOps #DeployFirst #Payvision… "
Jeff Cohen on Twitter: "Software architecture is rarely visualized, other than stick figures or flowcharts. UML was the last attempt I know of, and it failed under its own weight. What if there was a Google Maps for software architecture? What would you see? What would you do with it?"
William Louth on Twitter: "All these software developers who can’t seem to extract/define/create an appropriate model and interface for a bunch of code blocks are somehow going to create well designed microservices API? Right....."
Andrea Francia on Twitter: "The “distribulith” is the architectural style that combines the immobility of monoliths with fragility of microservices. Applied thoroughly, it helps the developer to fill his resumes with the technologies needed to be hired by the next company, while dooming the current one."
DHH on Twitter: "Microservices is not so much a technical pattern as a Keynesian one. Stimulating the economy by requiring three programmers to screw in the lightbulbs that used to take one. I strongly support its use at Big Cos and in downturns 😄👍"
Andrew Hallam on Twitter: "Architecting your documentation is just as important as architecting your system"
⚡Julia Evans⚡ sur Twitter : "here is a zine page on design that I'm working on! https://t.co/PgoE4PMnef"
Architecte Entreprise, Architecte Solutions et Expert Technique : Tout n'est qu'une question de focale
Nate Schutta on Twitter: "Architecture as a Service. AaaS. Pronounced just like you think. No one could have predicted this. @simonbrown #OReillySACon https://t.co/IwLEkdZbF8"
Gabriel PREDA on Twitter: "Put "architects" back to work... Like writing code... #INGLovesIT #Bucharest (great slide from @KrisBuytaert) https://t.co/nC7UsZCIJx"
Yves Hanoulle on Twitter: "architect is a title for senior people: is a nice way to say you are old @KevlinHenney at #oop2017"
Baptiste Mathus on Twitter: "Quand une entreprise qui se prétend mondiale parle de faire des trucs impactants "la nuit". Tu sens qu'il y a encore un long chemin à faire…"
Jeff Atwood on Twitter: "Working code attracts people who want to code. Design documents attract people who want to talk."
Scott W. Ambler on Twitter: "Proving architecture with working code vs. describing it with powerpoint is a hallmark of effective architects."
Grady Booch on Twitter: "Real code is to false architects as water was to the Wicked Witch of the West. https://t.co/vrcU04eHRy"
Anne Gabrillagues on Twitter: "Un architecte qui ne code pas est dangereux pour les projets ! #AgilePaysBasque"
James Roper on Twitter: "10 years ago, backends were monolithic services and frontends many pages. Now frontends are monolithic pages and backends many services."
Programming Wisdom on Twitter: ""If you're willing to restrict the flexibility of your approach, you can almost always do something better." - John Carmack (id Software) 😀"
[sjonsson] "If architects don’t write code, they are PowerPoint architects. They have no idea what is going on in the code.” @johannarothman at #Path15