kimtth/software-architect-mindmap: a curated architecture reference list with one editable mindmap

What kimtth/software-architect-mindmap actually contains

The repository is not a library and not a framework. The README states it was initially created for the mind map and is currently used as a curated collection of software architecture references. The top level holds a README, a Glossary.md, a LICENSE, a Preview.png, two mindmap artifacts (Software Architecture_Mindmap.json and Software_Architecture_Mindmap.png) and a files/ directory. The README also notes the mindmap is based on the Fresco Play curriculum, the internal learning platform of Tata Consultancy Services, dated 2022. That provenance matters: the map reflects one corporate curriculum, not a neutral survey of the field. The target reader is someone who wants a starting index of terminology and concepts across application development, cloud computing and data science, and who is willing to follow links outward rather than read a single self-contained document.

The mindmap JSON is the only editable artifact

Everything else in the repository is a list of outbound links, which the project cannot control and does not verify. The mindmap is different. The README's tip says the mindmap can be opened and edited using mindmap-maker-clean, a separate repository by the same author, and that this tool can convert the JSON source into a high-resolution PNG. The README states this was verified on Chrome and Firefox. So the data flow is: edit the JSON in the browser-based tool, export a PNG. There is no build step, no server, no CLI in this repository. If you want to change the map, you are editing JSON by hand or through that companion tool. That is a real constraint: the repository ships the data, not the editor.

Getting the mindmap open and exported

There is nothing to install in the usual sense. The repository has no package manifest and the README gives no setup steps, so the only concrete instruction is to obtain the files and then use the companion tool the README names. The README's tip points to mindmap-maker-clean for opening and editing the mindmap, and for converting the JSON source into a high-resolution PNG. Follow that repository for its own usage instructions; this repository does not document them. The README does say the tool was verified on Chrome and Firefox, so a Chromium or Firefox browser is the expected environment. One detail worth noting before you script anything: the JSON filename contains a space (Software Architecture_Mindmap.json), so quote the path in any shell command that touches it. The README does not describe the JSON schema, so the node structure is something you inspect by opening the file.

Where the reference list is strong and where it is thin

The README's contents section is organized, which is more than most link dumps manage. It separates industry trends and trend reports (Gartner, DORA, InfoQ, Thoughtworks Technology Radar, Trendshift), cloud architecture, engineering blogs, computer science courses, mini-books, tooling, computer science papers, and data science material. The papers section is split into named collections, including distributed systems and NLP. The tools section has subcategories for algorithm visualization, best practices, design patterns, diagramming tools, research tools and transformer architecture. The weakness is that these are pointers. The README does not annotate most entries, so a link titled "Awesome System Design Resources" tells you nothing about depth, currency or overlap with the four or five other system design lists nearby. Several entries are near-duplicates, for example two separate links to Software Architecture Books. The Glossary.md file is not described in the README at all, so its scope is something you have to open and judge.

The Fresco Play provenance and what it limits

The README is explicit that the mindmap is based on the Fresco Play curriculum and carries a 2022 copyright notice. An internal learning platform curriculum is built to serve one employer's training path, and the README itself, in a commented-out block, notes that it does not cover all IT topics. So treat the map as a study aid for that curriculum's vocabulary rather than as a complete taxonomy of the discipline. The repository was last pushed on 2026-07-27, so the link collection is being touched, but the mindmap's stated basis is older. If you are looking for a map of current practice, the map is the wrong artifact and the reference list is the better half of the repository.

Alternatives: the mindmap versus the awesome-list format

The obvious alternative is a dedicated awesome list such as Awesome Software Architecture, which the README itself links to and which is built purely as a categorized index of articles, videos and resources. The difference in approach is the artifact. An awesome list gives you prose pointers and lets you decide what to read; kimtth/software-architect-mindmap gives you a JSON node tree you can restructure and export as an image, plus a reference list that overlaps heavily with the awesome lists it cites. If your goal is a diagram to put in a slide deck or a study sheet, the JSON is the reason to pick this repository. If your goal is a reading queue, the awesome list format is more direct, because you are not maintaining JSON to get it. A second alternative is the companion repository mindmap-maker-clean itself, which is where the editing and PNG export actually happen; this repository is the data that tool consumes.

Licence and maintenance cost

The repository is MIT licensed, which permits reuse and modification with the usual attribution and warranty disclaimer conditions. That covers the repository contents. It does not cover the third-party material the README links to, including the Trendshift badge, the Gartner and InfoQ pages, or the PDFs under files/. The README notes downloaded PDFs for InfoQ trend reports and Thoughtworks Technology Radar volumes, and those PDFs carry their own terms; the repository does not restate them. On maintenance, the last push was on 2026-07-27, so the repository has been touched within the last two months. The upgrade cost is low in the software sense because there is no dependency graph to track. The real cost is link rot: every entry in the reference list is an external URL that can move or disappear, and nothing in the repository checks them. Budget time for that rather than for version upgrades.

Editorial conclusion

Adopt it if you want a link index for architecture, cloud and data science topics, or if you want to edit and export the mindmap JSON with mindmap-maker-clean. Do not adopt it if you need a runnable Python library or a maintained tool; the README states the repository is now a curated collection of references, not the original mindmap project. Before relying on it, open Software Architecture_Mindmap.json and check that its node structure covers the areas you care about, then confirm the files/ directory still holds the PDFs the README links to.

Frequently asked questions

Official sources

1. Issues
2. kimtth/software-architect-mindmap on GitHub
3. License: MIT
4. README