diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml new file mode 100644 index 0000000..7525c8f --- /dev/null +++ b/.github/workflows/ci.yml @@ -0,0 +1,27 @@ +name: ci +on: + - push + - pull_request +concurrency: + group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.sha }} + cancel-in-progress: true +jobs: + ci: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - uses: mikefarah/yq@v4.44.1 + - run: git submodule update --init + - run: COLOR=1 ./make.sh + env: + GITHUB_TOKEN: ${{ secrets._GITHUB_TOKEN }} + DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }} + signed: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + - run: git submodule update --init + - run: COLOR=1 ./ci/sub/bin/ensure_signed.sh + env: + GITHUB_TOKEN: ${{ secrets._GITHUB_TOKEN }} + DISCORD_WEBHOOK_URL: ${{ secrets.DISCORD_WEBHOOK_URL }} diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e43b0f9 --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +.DS_Store diff --git a/.gitmodules b/.gitmodules new file mode 100644 index 0000000..746c9e5 --- /dev/null +++ b/.gitmodules @@ -0,0 +1,3 @@ +[submodule "ci/sub"] + path = ci/sub + url = https://github.com/terrastruct/ci diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..114d4d3 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,44 @@ +# Contributing a diagram + +Whether you'd like to promote your content or just share a resource and help the +community, your contribution is much appreciated. + +To do so is very simple! But in order for the website generator to pick up your diagram, +it must follow a straightforward format: + +1. Create a directory under `diagrams/[year]/[month]/[day]/[name]`. That is the date you + are submitting it. Choose a short, descriptive name. Hyphenate it if multiple words. +2. Create a `diagram.yml` and fill out the template below. +3. Add referenced diagram images, e.g. `1.png`. The extension does not matter, so long as + you reference it in `diagram.yml` correctly. +4. Once a pull request is opened, it will be promptly reviewed and show up on the website + within 24 hours of merging. + +## `diagram.yml` template + +```yaml +schema-version: 0.1 + +# Required +name: "Green eggs and ham" +images: + - 1.png +attribution: "https://en.wikipedia.org/wiki/Green_Eggs_and_Ham" +tags: + - eggs + +# Optional +author: Dr. Seuss +description: | + Green Eggs and Ham is a children's book by Dr. Seuss. It was published by the Beginner Books imprint of Random House on August 12, 1960. +``` + +### Notes + +- You may include multiple images if relevant. They will be displayed like a horizontal + gallery. +- Please include the author if possible. Sometimes it's obvious, e.g. blog post authors. + But sometimes a low-effort search is all it takes, e.g. most open-source documentation + have Git commits showing the original committer of the diagram. +- For the description, a few sentences of text around the diagram briefly explaining it is + enough. diff --git a/LICENSE.txt b/LICENSE.txt new file mode 100644 index 0000000..117cd8d --- /dev/null +++ b/LICENSE.txt @@ -0,0 +1,427 @@ +Attribution-ShareAlike 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution-ShareAlike 4.0 International Public +License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution-ShareAlike 4.0 International Public License ("Public +License"). To the extent this Public License may be interpreted as a +contract, You are granted the Licensed Rights in consideration of Your +acceptance of these terms and conditions, and the Licensor grants You +such rights in consideration of benefits the Licensor receives from +making the Licensed Material available under these terms and +conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. BY-SA Compatible License means a license listed at + creativecommons.org/compatiblelicenses, approved by Creative + Commons as essentially the equivalent of this Public License. + + d. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + e. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + f. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + g. License Elements means the license attributes listed in the name + of a Creative Commons Public License. The License Elements of this + Public License are Attribution and ShareAlike. + + h. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + i. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + j. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + k. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + l. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + m. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. Additional offer from the Licensor -- Adapted Material. + Every recipient of Adapted Material from You + automatically receives an offer from the Licensor to + exercise the Licensed Rights in the Adapted Material + under the conditions of the Adapter's License You apply. + + c. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + b. ShareAlike. + + In addition to the conditions in Section 3(a), if You Share + Adapted Material You produce, the following conditions also apply. + + 1. The Adapter's License You apply must be a Creative Commons + license with the same License Elements, this version or + later, or a BY-SA Compatible License. + + 2. You must include the text of, or the URI or hyperlink to, the + Adapter's License You apply. You may satisfy this condition + in any reasonable manner based on the medium, means, and + context in which You Share Adapted Material. + + 3. You may not offer or impose any additional or different terms + or conditions on, or apply any Effective Technological + Measures to, Adapted Material that restrict exercise of the + rights granted under the Adapter's License You apply. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material, + + including for purposes of Section 3(b); and + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + +Creative Commons may be contacted at creativecommons.org. diff --git a/README.md b/README.md new file mode 100644 index 0000000..c54825f --- /dev/null +++ b/README.md @@ -0,0 +1,14 @@ +
+ D2 +

+ A collection of software architecture diagrams +

+ +[![ci](https://github.com/terrastruct/awesome-diagrams/actions/workflows/ci.yml/badge.svg)](https://github.com/terrastruct/awesome-diagrams/actions/workflows/ci.yml) +[![license](https://img.shields.io/github/license/terrastruct/awesome-diagrams?color=9cf)](./LICENSE.txt) +
+ +This repository is the content for +[https://softwarediagrams.com](https://softwarediagrams.com). + +To contribute a diagram, please see [CONTRIBUTING.md](CONTRIBUTING.md). diff --git a/collections/auth/1.svg b/collections/auth/1.svg new file mode 100644 index 0000000..a19a9a3 --- /dev/null +++ b/collections/auth/1.svg @@ -0,0 +1,2022 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/collections/auth/collection.yml b/collections/auth/collection.yml new file mode 100644 index 0000000..304aa96 --- /dev/null +++ b/collections/auth/collection.yml @@ -0,0 +1,10 @@ +schema-version: 0.1 +name: Authentication flows +diagrams: + - 2024/05/12/auth0 + - 2024/05/12/google-sso + - 2024/05/12/okta + - 2024/05/12/workos +banner: + image: 1.svg + background-color: '#EEF2FF' diff --git a/collections/payment-systems/1.svg b/collections/payment-systems/1.svg new file mode 100644 index 0000000..4452636 --- /dev/null +++ b/collections/payment-systems/1.svg @@ -0,0 +1,2977 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/collections/payment-systems/collection.yml b/collections/payment-systems/collection.yml new file mode 100644 index 0000000..9484108 --- /dev/null +++ b/collections/payment-systems/collection.yml @@ -0,0 +1,9 @@ +schema-version: 0.1 +name: Payment systems +diagrams: + - 2024/05/08/adyen-payment-lifecycle + - 2024/05/08/mastercard-processing + - 2024/05/08/brex-cash-infrastructure +banner: + image: 1.svg + background-color: '#EFFCED' diff --git a/diagrams/2024/05/03/kubernetes-cluster/1.svg b/diagrams/2024/05/03/kubernetes-cluster/1.svg new file mode 100644 index 0000000..ecc2444 --- /dev/null +++ b/diagrams/2024/05/03/kubernetes-cluster/1.svg @@ -0,0 +1,3 @@ + + +
Node 1
Node 1
Node 2
Node 2
kube-scheduler
kube-scheduler
kube-controller-manager
kube-controller-manager
CLOUD PROVIDER API
CLOUD PROVIDER API
CRI
CRI
CRI
CRI
CONTROL PLANE
CONTROL PLANE
CLUSTER
CLUSTER
etcd
etcd
kube-api-server
kube-api-server
scheduler
scheduler
Controller Manager
Controller Manager
cloud-control-manager
cloud-control-manager
kubelet
kubelet
kube-proxy
kube-proxy
kubelet
kubelet
kube-proxy
kube-proxy
pod
pod
pod
pod
pod
pod
pod
pod diff --git a/diagrams/2024/05/03/kubernetes-cluster/diagram.yml b/diagrams/2024/05/03/kubernetes-cluster/diagram.yml new file mode 100644 index 0000000..9c8dcc3 --- /dev/null +++ b/diagrams/2024/05/03/kubernetes-cluster/diagram.yml @@ -0,0 +1,11 @@ +schema-version: 0.1 +# Required +name: Kubernetes cluster architecture +images: + - 1.svg +attribution: https://kubernetes.io/docs/concepts/architecture/ +tags: + - kubernetes +# Optional +author: Utkarsh Singh +description: Kubernetes cluster architecture diff --git a/diagrams/2024/05/04/airflow/1.png b/diagrams/2024/05/04/airflow/1.png new file mode 100644 index 0000000..94a0590 Binary files /dev/null and b/diagrams/2024/05/04/airflow/1.png differ diff --git a/diagrams/2024/05/04/airflow/diagram.yml b/diagrams/2024/05/04/airflow/diagram.yml new file mode 100644 index 0000000..461b901 --- /dev/null +++ b/diagrams/2024/05/04/airflow/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Basic Airflow deployment +images: + - 1.png +attribution: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/overview.html +tags: + - airflow + - python +# Optional +author: Jarek Potiuk +description: | + This is the simplest deployment of Airflow, usually operated and managed on a single machine. Such a deployment usually uses the LocalExecutor, where the scheduler and the workers are in the same Python process and the DAG files are read directly from the local filesystem by the scheduler. The webserver runs on the same machine as the scheduler. There is no triggerer component, which means that task deferral is not possible. diff --git a/diagrams/2024/05/04/envoy/1.svg b/diagrams/2024/05/04/envoy/1.svg new file mode 100644 index 0000000..e7446e6 --- /dev/null +++ b/diagrams/2024/05/04/envoy/1.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/diagrams/2024/05/04/envoy/2.svg b/diagrams/2024/05/04/envoy/2.svg new file mode 100644 index 0000000..e0112d9 --- /dev/null +++ b/diagrams/2024/05/04/envoy/2.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/diagrams/2024/05/04/envoy/3.svg b/diagrams/2024/05/04/envoy/3.svg new file mode 100644 index 0000000..7ccc858 --- /dev/null +++ b/diagrams/2024/05/04/envoy/3.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/diagrams/2024/05/04/envoy/4.svg b/diagrams/2024/05/04/envoy/4.svg new file mode 100644 index 0000000..e210d85 --- /dev/null +++ b/diagrams/2024/05/04/envoy/4.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/diagrams/2024/05/04/envoy/diagram.yml b/diagrams/2024/05/04/envoy/diagram.yml new file mode 100644 index 0000000..b304651 --- /dev/null +++ b/diagrams/2024/05/04/envoy/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 +# Required +name: Envoy network topology +images: + - 1.svg + - 2.svg + - 3.svg + - 4.svg +attribution: https://www.envoyproxy.io/docs/envoy/latest/intro/life_of_a_request +tags: + - envoy + - network +# Optional +author: htuch +description: | + How a request flows through the components in a network (including Envoy) depends on the network’s topology. Envoy can be used in a wide variety of networking topologies. diff --git a/diagrams/2024/05/04/istio/1.svg b/diagrams/2024/05/04/istio/1.svg new file mode 100644 index 0000000..72f273d --- /dev/null +++ b/diagrams/2024/05/04/istio/1.svg @@ -0,0 +1 @@ +archIstio MeshIngresstrafficEgresstrafficService AProxyService BProxyDiscoveryConfigurationCertificatesMesh trafficControl planeDataplaneistiodGalleyPilotCitadel \ No newline at end of file diff --git a/diagrams/2024/05/04/istio/diagram.yml b/diagrams/2024/05/04/istio/diagram.yml new file mode 100644 index 0000000..47c17e6 --- /dev/null +++ b/diagrams/2024/05/04/istio/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Istio architecture +images: + - 1.svg +attribution: https://istio.io/latest/docs/ops/deployment/architecture/ +tags: + - istio + - envoy + - kubernetes +# Optional +author: Frank Budinsky +description: | + An Istio service mesh is logically split into a data plane and a control plane. + + The data plane is composed of a set of intelligent proxies (Envoy) deployed as sidecars. These proxies mediate and control all network communication between microservices. They also collect and report telemetry on all mesh traffic. + + The control plane manages and configures the proxies to route traffic. diff --git a/diagrams/2024/05/04/kafka/1.jpg b/diagrams/2024/05/04/kafka/1.jpg new file mode 100644 index 0000000..9222079 Binary files /dev/null and b/diagrams/2024/05/04/kafka/1.jpg differ diff --git a/diagrams/2024/05/04/kafka/diagram.yml b/diagrams/2024/05/04/kafka/diagram.yml new file mode 100644 index 0000000..bb6764a --- /dev/null +++ b/diagrams/2024/05/04/kafka/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: Kafka Streams +images: + - 1.jpg +attribution: https://kafka.apache.org/37/documentation/streams/architecture +tags: + - kafka +# Optional +author: +description: | + Kafka Streams simplifies application development by building on the Kafka producer and consumer libraries and leveraging the native capabilities of Kafka to offer data parallelism, distributed coordination, fault tolerance, and operational simplicity. diff --git a/diagrams/2024/05/04/llm/1.webp b/diagrams/2024/05/04/llm/1.webp new file mode 100644 index 0000000..b60a2ff Binary files /dev/null and b/diagrams/2024/05/04/llm/1.webp differ diff --git a/diagrams/2024/05/04/llm/diagram.yml b/diagrams/2024/05/04/llm/diagram.yml new file mode 100644 index 0000000..3976c29 --- /dev/null +++ b/diagrams/2024/05/04/llm/diagram.yml @@ -0,0 +1,15 @@ +schema-version: 0.1 +# Required +name: How to train your own Large Language Models +images: + - 1.webp +attribution: https://blog.replit.com/llm-training +tags: + - llm + - replit + - ai + - google-cloud +# Optional +author: The AI Team @ Replit +description: | + How Replit trains Large Language Models (LLMs) using Databricks, Hugging Face, and MosaicML. diff --git a/diagrams/2024/05/04/tpu/1.webp b/diagrams/2024/05/04/tpu/1.webp new file mode 100644 index 0000000..aadf6b1 Binary files /dev/null and b/diagrams/2024/05/04/tpu/1.webp differ diff --git a/diagrams/2024/05/04/tpu/diagram.yml b/diagrams/2024/05/04/tpu/diagram.yml new file mode 100644 index 0000000..fa32d25 --- /dev/null +++ b/diagrams/2024/05/04/tpu/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Cloud TPU in GKE +images: + - 1.webp +attribution: https://cloud.google.com/tpu +tags: + - tpu + - google-cloud +# Optional +author: +description: | + Combine the power of Cloud TPUs with the flexibility and scalability of GKE to build and deploy machine learning models faster and more easily than ever before. With Cloud TPUs available in GKE, you can now have a single consistent operations environment for all your workloads, standardizing automated MLOps pipelines. diff --git a/diagrams/2024/05/05/activemq/1.avif b/diagrams/2024/05/05/activemq/1.avif new file mode 100644 index 0000000..6bf9dc6 Binary files /dev/null and b/diagrams/2024/05/05/activemq/1.avif differ diff --git a/diagrams/2024/05/05/activemq/diagram.yml b/diagrams/2024/05/05/activemq/diagram.yml new file mode 100644 index 0000000..bac8385 --- /dev/null +++ b/diagrams/2024/05/05/activemq/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: ActiveMQ Classic architecture +images: + - 1.avif +attribution: https://www.datadoghq.com/blog/activemq-architecture-and-metrics/ +tags: + - message-queue + - activemq +# Optional +author: David M. Lentz +description: | + ActiveMQ sends messages between client applications—producers, which create messages and submit them for delivery, and consumers, which receive and process messages. The ActiveMQ broker routes each message through a messaging endpoint called a destination (in ActiveMQ Classic) or an address (in Artemis). Both ActiveMQ versions are capable of point-to-point messaging—in which the broker routes each message to one of the available consumers in a round-robin pattern—and publish/subscribe (or “pub/sub”) messaging—in which the broker delivers each message to every consumer that is subscribed to the topic (in ActiveMQ Classic) or address (in ActiveMQ Artemis). diff --git a/diagrams/2024/05/05/jenkins/1.png b/diagrams/2024/05/05/jenkins/1.png new file mode 100644 index 0000000..4bec9e3 Binary files /dev/null and b/diagrams/2024/05/05/jenkins/1.png differ diff --git a/diagrams/2024/05/05/jenkins/diagram.yml b/diagrams/2024/05/05/jenkins/diagram.yml new file mode 100644 index 0000000..b2ac1f2 --- /dev/null +++ b/diagrams/2024/05/05/jenkins/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 +# Required +name: Jenkins architecture +images: + - 1.png +attribution: https://www.jenkins.io/doc/developer/architecture/ +tags: + - jenkins + - ci/cd + - drawio +# Optional +author: Angélique Jard +description: | + This dataflow represents Jenkins as a "box". The goal is to have a view of network flow that goes in and out. + + This diagram is a high level view centered on Jenkins core. diff --git a/diagrams/2024/05/05/mongodb/1.png b/diagrams/2024/05/05/mongodb/1.png new file mode 100644 index 0000000..9eb324c Binary files /dev/null and b/diagrams/2024/05/05/mongodb/1.png differ diff --git a/diagrams/2024/05/05/mongodb/diagram.yml b/diagrams/2024/05/05/mongodb/diagram.yml new file mode 100644 index 0000000..5de00c6 --- /dev/null +++ b/diagrams/2024/05/05/mongodb/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: MongoDB's Application data platform +images: + - 1.png +attribution: https://www.mongodb.com/collateral/mongodb-architecture-guide +tags: + - mongodb + - database +# Optional +author: +description: | + Building on MongoDB’s document data model, expressive Query API, and distributed systems DNA, the MongoDB Atlas application data platform delivers a cohesive and integrated set of data and database services. Atlas streamlines how teams work with data, specifically in the context of building software and systems that deliver real-time experiences to both end customers and internal users diff --git a/diagrams/2024/05/05/pytorch/1.png b/diagrams/2024/05/05/pytorch/1.png new file mode 100644 index 0000000..d69e2aa Binary files /dev/null and b/diagrams/2024/05/05/pytorch/1.png differ diff --git a/diagrams/2024/05/05/pytorch/diagram.yml b/diagrams/2024/05/05/pytorch/diagram.yml new file mode 100644 index 0000000..e0139f3 --- /dev/null +++ b/diagrams/2024/05/05/pytorch/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Pytorch architecture +images: + - 1.png +attribution: https://pytorch.org/executorch/stable/getting-started-architecture +tags: + - pytorch + - python +# Optional +author: Martin Yuan +description: | + There are three phases to deploy a PyTorch model to on-device: program preparation, runtime preparation, and program execution, as shown in the diagram below, with a number of user entry points. diff --git a/diagrams/2024/05/05/traefik/1.webp b/diagrams/2024/05/05/traefik/1.webp new file mode 100644 index 0000000..0181234 Binary files /dev/null and b/diagrams/2024/05/05/traefik/1.webp differ diff --git a/diagrams/2024/05/05/traefik/diagram.yml b/diagrams/2024/05/05/traefik/diagram.yml new file mode 100644 index 0000000..4b83264 --- /dev/null +++ b/diagrams/2024/05/05/traefik/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Traefik Enterprise architecture +images: + - 1.webp +attribution: https://doc.traefik.io/traefik-enterprise/concepts/ +tags: + - traefik + - networking + - golang +# Optional +author: +description: | + Traefik Enterprise's architecture consists of nodes spread into two different planes: the control plane and the data plane. The notions of control plane and data plane are well-known patterns and are not specific to Traefik Enterprise. diff --git a/diagrams/2024/05/05/vercel/1.avif b/diagrams/2024/05/05/vercel/1.avif new file mode 100644 index 0000000..6df6d45 Binary files /dev/null and b/diagrams/2024/05/05/vercel/1.avif differ diff --git a/diagrams/2024/05/05/vercel/diagram.yml b/diagrams/2024/05/05/vercel/diagram.yml new file mode 100644 index 0000000..61f9ae0 --- /dev/null +++ b/diagrams/2024/05/05/vercel/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Vercel deployment and lifecycle +images: + - 1.avif +attribution: https://vercel.com/blog/behind-the-scenes-of-vercels-infrastructure +tags: + - vercel + - deployment +# Optional +author: Lydia Hallie +description: | + Deployments start with code written in one of the over 35 frameworks supported by Vercel, or by using the Build Output API. Deployments can be created through the Vercel CLI or by pushing code to your git repository. The Vercel Git integration automatically listens for your commit and triggers a new deployment. diff --git a/diagrams/2024/05/06/traefik/1.webp b/diagrams/2024/05/06/traefik/1.webp new file mode 100644 index 0000000..026c502 Binary files /dev/null and b/diagrams/2024/05/06/traefik/1.webp differ diff --git a/diagrams/2024/05/06/traefik/diagram.yml b/diagrams/2024/05/06/traefik/diagram.yml new file mode 100644 index 0000000..4ca91ba --- /dev/null +++ b/diagrams/2024/05/06/traefik/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Traefik Services +images: + - 1.webp +attribution: https://doc.traefik.io/traefik/routing/services/ +tags: + - traefik + - golang + - networking +# Optional +author: Jean-Baptiste Doumenjou +description: | + The Traefik Services are responsible for configuring how to reach the actual services that will eventually handle the incoming requests. diff --git a/diagrams/2024/05/08/adyen-payment-lifecycle/1.svg b/diagrams/2024/05/08/adyen-payment-lifecycle/1.svg new file mode 100644 index 0000000..9d1a8d1 --- /dev/null +++ b/diagrams/2024/05/08/adyen-payment-lifecycle/1.svg @@ -0,0 +1,80 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/diagrams/2024/05/08/adyen-payment-lifecycle/diagram.yml b/diagrams/2024/05/08/adyen-payment-lifecycle/diagram.yml new file mode 100644 index 0000000..4dafe08 --- /dev/null +++ b/diagrams/2024/05/08/adyen-payment-lifecycle/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: Adyen Payments lifecycle +images: + - 1.svg +attribution: https://docs.adyen.com/account/payments-lifecycle/?tab=successful_payment_1 +tags: + - payments + - adyen +# Optional +author: +description: diff --git a/diagrams/2024/05/08/brex-cash-infrastructure/1.webp b/diagrams/2024/05/08/brex-cash-infrastructure/1.webp new file mode 100644 index 0000000..68ace39 Binary files /dev/null and b/diagrams/2024/05/08/brex-cash-infrastructure/1.webp differ diff --git a/diagrams/2024/05/08/brex-cash-infrastructure/diagram.yml b/diagrams/2024/05/08/brex-cash-infrastructure/diagram.yml new file mode 100644 index 0000000..c9af05c --- /dev/null +++ b/diagrams/2024/05/08/brex-cash-infrastructure/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: Brex Cash infrastructure +images: + - 1.webp +attribution: https://medium.com/brexeng/how-brex-cash-moves-your-money-edb15982c2 +tags: + - payments + - brex +# Optional +author: Ross Semenov +description: diff --git a/diagrams/2024/05/08/mastercard-processing/1.svg b/diagrams/2024/05/08/mastercard-processing/1.svg new file mode 100644 index 0000000..50ccab7 --- /dev/null +++ b/diagrams/2024/05/08/mastercard-processing/1.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/diagrams/2024/05/08/mastercard-processing/diagram.yml b/diagrams/2024/05/08/mastercard-processing/diagram.yml new file mode 100644 index 0000000..f865cfc --- /dev/null +++ b/diagrams/2024/05/08/mastercard-processing/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Mastercard processing +images: + - 1.svg +attribution: https://developer.mastercard.com/product/mastercard-processing/ +tags: + - payments + - mastercard +# Optional +author: +description: | + Mastercard Processing APIs cover the entire product lifecycle, from setting up a client, creating accounts, and ordering a card that can be instantly tokenized. All kinds of mobile PAYs and wearables are supported, such as Apple, Google, Samsung, Xiaomi, Fitbit, Garmin, Swatch, Card on File, and Issuer Wallet (HCE). diff --git a/diagrams/2024/05/08/visa-apis/1.png b/diagrams/2024/05/08/visa-apis/1.png new file mode 100644 index 0000000..7650a14 Binary files /dev/null and b/diagrams/2024/05/08/visa-apis/1.png differ diff --git a/diagrams/2024/05/08/visa-apis/diagram.yml b/diagrams/2024/05/08/visa-apis/diagram.yml new file mode 100644 index 0000000..dad05b4 --- /dev/null +++ b/diagrams/2024/05/08/visa-apis/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Visa APIs +images: + - 1.png +attribution: https://developer.visa.com/pages/working-with-visa-apis +tags: + - payments + - visa +# Optional +author: +description: | + Visa Developer Platform helps consolidate multiple partner and developer facing assets across Visa into a common platform to simplify partner connectivity. Visa’s API management features can help accelerate the pace of collaboration and innovation within Visa and between its strategic partner, by providing them with a one stop shop for API availability. The API management platform becomes an API “portal” where developers across the B2B/B2C space can efficiently leverage Visa APIs. diff --git a/diagrams/2024/05/09/rivet/1.png b/diagrams/2024/05/09/rivet/1.png new file mode 100644 index 0000000..c10bc28 Binary files /dev/null and b/diagrams/2024/05/09/rivet/1.png differ diff --git a/diagrams/2024/05/09/rivet/diagram.yml b/diagrams/2024/05/09/rivet/diagram.yml new file mode 100644 index 0000000..2d13486 --- /dev/null +++ b/diagrams/2024/05/09/rivet/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Rivet Architecture +images: + - 1.png +attribution: https://github.com/rivet-gg/rivet +tags: + - rivet + - figma +# Optional +author: Nathan Flurry +description: | + Open-source solution to deploy, scale, and operate your multiplayer game. diff --git a/diagrams/2024/05/11/flux/1.png b/diagrams/2024/05/11/flux/1.png new file mode 100644 index 0000000..2c43d4b Binary files /dev/null and b/diagrams/2024/05/11/flux/1.png differ diff --git a/diagrams/2024/05/11/flux/diagram.yml b/diagrams/2024/05/11/flux/diagram.yml new file mode 100644 index 0000000..e197088 --- /dev/null +++ b/diagrams/2024/05/11/flux/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Flux architecture +images: + - 1.png +attribution: http://fluxxor.com/what-is-flux.html +tags: + - flux + - frontend + - react +# Optional +author: Michelle Tilley +description: | + Flux is an architecture for creating data layers in JavaScript applications. It was designed at Facebook along with the React view library. It places a focus on creating explicit and understandable update paths for your application's data, which makes tracing changes during development simpler and makes bugs easier to track down and fix. diff --git a/diagrams/2024/05/12/acrolinx-platform/1.png b/diagrams/2024/05/12/acrolinx-platform/1.png new file mode 100644 index 0000000..0e01482 Binary files /dev/null and b/diagrams/2024/05/12/acrolinx-platform/1.png differ diff --git a/diagrams/2024/05/12/acrolinx-platform/2.png b/diagrams/2024/05/12/acrolinx-platform/2.png new file mode 100644 index 0000000..dc2b38d Binary files /dev/null and b/diagrams/2024/05/12/acrolinx-platform/2.png differ diff --git a/diagrams/2024/05/12/acrolinx-platform/3.png b/diagrams/2024/05/12/acrolinx-platform/3.png new file mode 100644 index 0000000..8fb3e49 Binary files /dev/null and b/diagrams/2024/05/12/acrolinx-platform/3.png differ diff --git a/diagrams/2024/05/12/acrolinx-platform/4.png b/diagrams/2024/05/12/acrolinx-platform/4.png new file mode 100644 index 0000000..b10a90c Binary files /dev/null and b/diagrams/2024/05/12/acrolinx-platform/4.png differ diff --git a/diagrams/2024/05/12/acrolinx-platform/diagram.yml b/diagrams/2024/05/12/acrolinx-platform/diagram.yml new file mode 100644 index 0000000..9e5b476 --- /dev/null +++ b/diagrams/2024/05/12/acrolinx-platform/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Acrolinx Platform +images: + - 1.png + - 2.png + - 3.png + - 4.png +attribution: https://support.acrolinx.com/hc/en-us/articles/10210859500818-Architecture-Diagrams +tags: + - auth + - infrastructure +# Optional +author: Acrolinx team +description: | + Acrolinx provides an AI service to help you write copy. These are the + architecture diagrams of its platform, including views for its cloud, + containers, scalability, and authentication. diff --git a/diagrams/2024/05/12/auth0/1.png b/diagrams/2024/05/12/auth0/1.png new file mode 100644 index 0000000..83a4f8a Binary files /dev/null and b/diagrams/2024/05/12/auth0/1.png differ diff --git a/diagrams/2024/05/12/auth0/diagram.yml b/diagrams/2024/05/12/auth0/diagram.yml new file mode 100644 index 0000000..0cffa68 --- /dev/null +++ b/diagrams/2024/05/12/auth0/diagram.yml @@ -0,0 +1,15 @@ +schema-version: 0.1 +# Required +name: Auth0 IdP +images: + - 1.png +attribution: https://auth0.com/docs/get-started/architecture-scenarios/multiple-organization-architecture/single-identity-provider-organizations +tags: + - auth0 + - auth +# Optional +author: +description: | + In the Single Identity Provider (IdP) Organizations scenario, every organization that uses the Auth0 Organizations feature uses exactly one Auth0 connection. This feature allows each application to select the appropriate organization defined on the Auth0 Tenant, which will either authenticate user credentials directly or forward the authentication request to the appropriate IdP to handle. + + Regardless of how credentials are processed--whether user credentials are stored in a database connection (like with Hoekstra & Associates) or are validated via an enterprise connection (like with MetaHexa Bank) or a social connection--your application behaves the same way. Leveraging the Organizations feature allows you to configure and control the experience. diff --git a/diagrams/2024/05/12/firebase/1.png b/diagrams/2024/05/12/firebase/1.png new file mode 100644 index 0000000..bca6a2b Binary files /dev/null and b/diagrams/2024/05/12/firebase/1.png differ diff --git a/diagrams/2024/05/12/firebase/diagram.yml b/diagrams/2024/05/12/firebase/diagram.yml new file mode 100644 index 0000000..027cc4f --- /dev/null +++ b/diagrams/2024/05/12/firebase/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: Firebase architecture +images: + - 1.png +attribution: https://firebase.google.com/docs/cloud-messaging/fcm-architecture +tags: + - firebase +# Optional +author: +description: | + FCM relies on the following set of components that build, transport, and receive messages diff --git a/diagrams/2024/05/12/google-sso/1.svg b/diagrams/2024/05/12/google-sso/1.svg new file mode 100644 index 0000000..0f42cc2 --- /dev/null +++ b/diagrams/2024/05/12/google-sso/1.svg @@ -0,0 +1,1074 @@ + + + + + + + + + + + + + + + + + + Diagram 3 + + Layer 1 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/diagrams/2024/05/12/google-sso/diagram.yml b/diagrams/2024/05/12/google-sso/diagram.yml new file mode 100644 index 0000000..1f46eaf --- /dev/null +++ b/diagrams/2024/05/12/google-sso/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Google SSO +images: + - 1.svg +attribution: https://cloud.google.com/architecture/identity/single-sign-on +tags: + - google + - auth +# Optional +author: +description: | + Cloud Identity and Google Workspace support Security Assertion Markup Language (SAML) 2.0 for single sign-on. SAML is an open standard for exchanging authentication and authorization data between a SAML IdP and SAML service providers. When you use SSO for Cloud Identity or Google Workspace, your external IdP is the SAML IdP and Google is the SAML service provider. diff --git a/diagrams/2024/05/12/okta/1.png b/diagrams/2024/05/12/okta/1.png new file mode 100644 index 0000000..c6c3f3d Binary files /dev/null and b/diagrams/2024/05/12/okta/1.png differ diff --git a/diagrams/2024/05/12/okta/2.png b/diagrams/2024/05/12/okta/2.png new file mode 100644 index 0000000..d06bfae Binary files /dev/null and b/diagrams/2024/05/12/okta/2.png differ diff --git a/diagrams/2024/05/12/okta/3.png b/diagrams/2024/05/12/okta/3.png new file mode 100644 index 0000000..3074cc0 Binary files /dev/null and b/diagrams/2024/05/12/okta/3.png differ diff --git a/diagrams/2024/05/12/okta/4.png b/diagrams/2024/05/12/okta/4.png new file mode 100644 index 0000000..f2686dd Binary files /dev/null and b/diagrams/2024/05/12/okta/4.png differ diff --git a/diagrams/2024/05/12/okta/diagram.yml b/diagrams/2024/05/12/okta/diagram.yml new file mode 100644 index 0000000..097dd68 --- /dev/null +++ b/diagrams/2024/05/12/okta/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Okta IAM architecture +images: + - 1.png + - 2.png + - 3.png + - 4.png +attribution: https://www.okta.com/resources/whitepaper/iam-architecture/ +tags: + - firebase + - auth +# Optional +author: +description: | + Enterprises use portals to manage access to web applications that serve customers and partners. Administrators often create these portals by assembling multiple behind-the-scenes web applications and services to form a complete solution. + + With Okta, organizations can quickly and easily automate all portal user management functionality and provide customers and partners with a seamless experience, all with a 100-percent ondemand, secure, highly available service. diff --git a/diagrams/2024/05/12/sentry/1.svg b/diagrams/2024/05/12/sentry/1.svg new file mode 100644 index 0000000..470e23d --- /dev/null +++ b/diagrams/2024/05/12/sentry/1.svg @@ -0,0 +1 @@ +
SDK
sentry.example.com/api/\d+/store/
sentry.example.com
Your Application
Load Balancer
relay
Sentry (web)
symbolicator
kafka
redis
snuba
memcached
postgres
clickhouse
zookeeper
Sentry (worker)
 \ No newline at end of file diff --git a/diagrams/2024/05/12/sentry/diagram.yml b/diagrams/2024/05/12/sentry/diagram.yml new file mode 100644 index 0000000..9504a70 --- /dev/null +++ b/diagrams/2024/05/12/sentry/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Sentry architecture +images: + - 1.svg +attribution: https://develop.sentry.dev/architecture/ +tags: + - sentry + - monitoring + - mermaid +# Optional +author: David Cramer +description: | + Edges represent service dependencies. diff --git a/diagrams/2024/05/12/workos/1.avif b/diagrams/2024/05/12/workos/1.avif new file mode 100644 index 0000000..3b805b1 Binary files /dev/null and b/diagrams/2024/05/12/workos/1.avif differ diff --git a/diagrams/2024/05/12/workos/diagram.yml b/diagrams/2024/05/12/workos/diagram.yml new file mode 100644 index 0000000..f4aa78a --- /dev/null +++ b/diagrams/2024/05/12/workos/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: WorkOS Single Sign-on +images: + - 1.avif +attribution: https://workos.com/docs/sso +tags: + - workos + - auth +# Optional +author: +description: | + WorkOS SSO API acts as authentication middleware and intentionally does not handle user database management for your application. This is by design, to minimize vendor lock-in. diff --git a/diagrams/2024/05/13/docker/1.webp b/diagrams/2024/05/13/docker/1.webp new file mode 100644 index 0000000..695c1be Binary files /dev/null and b/diagrams/2024/05/13/docker/1.webp differ diff --git a/diagrams/2024/05/13/docker/diagram.yml b/diagrams/2024/05/13/docker/diagram.yml new file mode 100644 index 0000000..e1ac5f3 --- /dev/null +++ b/diagrams/2024/05/13/docker/diagram.yml @@ -0,0 +1,20 @@ +schema-version: 0.1 +# Required +name: Docker architecture +images: + - 1.webp +attribution: https://docs.docker.com/get-started/overview/ +tags: + - docker + - containers + - infrastructure +# Optional +author: Allie Sadler +description: | + Docker uses a client-server architecture. The Docker client talks to the + Docker daemon, which does the heavy lifting of building, running, and + distributing your Docker containers. The Docker client and daemon can run on + the same system, or you can connect a Docker client to a remote Docker + daemon. The Docker client and daemon communicate using a REST API, over UNIX + sockets or a network interface. Another Docker client is Docker Compose, that + lets you work with applications consisting of a set of containers. diff --git a/diagrams/2024/05/13/jailbreak-llm/1.png b/diagrams/2024/05/13/jailbreak-llm/1.png new file mode 100644 index 0000000..e68da5f Binary files /dev/null and b/diagrams/2024/05/13/jailbreak-llm/1.png differ diff --git a/diagrams/2024/05/13/jailbreak-llm/diagram.yml b/diagrams/2024/05/13/jailbreak-llm/diagram.yml new file mode 100644 index 0000000..5b8bd03 --- /dev/null +++ b/diagrams/2024/05/13/jailbreak-llm/diagram.yml @@ -0,0 +1,19 @@ +schema-version: 0.1 +# Required +name: ASCII Art LLM Jailbreak +images: + - 1.png +attribution: https://arxiv.org/abs/2402.11753 +tags: + - llm + - ai + - ascii +# Optional +author: Luyao Niu +description: | + Overview of ArtPrompt. ArtPrompt consists of two steps. In the first step, + ArtPrompt masks the safety words (e.g., “bomb") within a prompt that could + result in rejection from the victim LLM. In the second step, ArtPrompt + replaces the masked word in Step I with ASCII art. Then the masked prompt is + combined with the ASCII art representation to form a cloaked prompt. The + cloaked prompt is finally sent to the victim LLM as a jailbreak attack. diff --git a/diagrams/2024/05/13/ragflow/1.png b/diagrams/2024/05/13/ragflow/1.png new file mode 100644 index 0000000..43d123d Binary files /dev/null and b/diagrams/2024/05/13/ragflow/1.png differ diff --git a/diagrams/2024/05/13/ragflow/diagram.yml b/diagrams/2024/05/13/ragflow/diagram.yml new file mode 100644 index 0000000..2615177 --- /dev/null +++ b/diagrams/2024/05/13/ragflow/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Ragflow system architecture +images: + - 1.png +attribution: https://github.com/infiniflow/ragflow +tags: + - llm + - ai + - rag +# Optional +author: KevinHuSh +description: | + RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine based on deep document understanding. diff --git a/diagrams/2024/05/14/jitsi/1.png b/diagrams/2024/05/14/jitsi/1.png new file mode 100644 index 0000000..cbc39f4 Binary files /dev/null and b/diagrams/2024/05/14/jitsi/1.png differ diff --git a/diagrams/2024/05/14/jitsi/diagram.yml b/diagrams/2024/05/14/jitsi/diagram.yml new file mode 100644 index 0000000..60f1f87 --- /dev/null +++ b/diagrams/2024/05/14/jitsi/diagram.yml @@ -0,0 +1,19 @@ +schema-version: 0.1 +# Required +name: Jitsi Meet architecture +images: + - 1.png +attribution: https://jitsi.github.io/handbook/docs/architecture/ +tags: + - streaming +# Optional +author: Kylian Kropf +description: | + The individual connections between the previously described components, as + well as their external integrations are described in the figure below. + + The external connections can be categorized into two main groups. Firstly, + the connections between clients that request a video or audio connection are + performed through remote requests and data streams. The second category of + external connections is those to external services that help store + recordings, stream recordings, stream videos, or help with creating meetings. diff --git a/diagrams/2024/05/14/slack-messaging/1.webp b/diagrams/2024/05/14/slack-messaging/1.webp new file mode 100644 index 0000000..ea752c7 Binary files /dev/null and b/diagrams/2024/05/14/slack-messaging/1.webp differ diff --git a/diagrams/2024/05/14/slack-messaging/2.webp b/diagrams/2024/05/14/slack-messaging/2.webp new file mode 100644 index 0000000..c5b2d00 Binary files /dev/null and b/diagrams/2024/05/14/slack-messaging/2.webp differ diff --git a/diagrams/2024/05/14/slack-messaging/3.webp b/diagrams/2024/05/14/slack-messaging/3.webp new file mode 100644 index 0000000..922457b Binary files /dev/null and b/diagrams/2024/05/14/slack-messaging/3.webp differ diff --git a/diagrams/2024/05/14/slack-messaging/diagram.yml b/diagrams/2024/05/14/slack-messaging/diagram.yml new file mode 100644 index 0000000..458e2f1 --- /dev/null +++ b/diagrams/2024/05/14/slack-messaging/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Slack real-time messaging +images: + - 1.webp + - 2.webp + - 3.webp +attribution: https://slack.engineering/real-time-messaging/ +tags: + - websocket +# Optional +author: Sameera Thangudu +description: | + Every Slack client has a persistent websocket connection to Slack’s servers to receive real-time events to maintain its state. + + Once the websocket is set up, as discussed above, the client hits our Webapp API to send a message. Webapp then sends that message to AS. AS looks at the channel ID in this message, discovers CS through a consistent hash ring, and routes the message to the appropriate CS that hosts the real time messaging for this channel. When CS receives the message for that channel, it sends out the message to every GS across the world that is subscribed to that channel. Each GS that receives that message sends it to every connected client subscribed to that channel id. + + Aside from chat messages, there is another special kind of message called an event. An event is any update a client receives in real time that changes the state of the client. There are hundreds of different types of events that flow across our servers. Some examples include when a user sends a reaction to a message, a bookmark is added, or a member joins a channel. These events follow a similar journey to the simple chat message shown above. diff --git a/diagrams/2024/05/15/netlify-connect/1.png b/diagrams/2024/05/15/netlify-connect/1.png new file mode 100644 index 0000000..9d5547f Binary files /dev/null and b/diagrams/2024/05/15/netlify-connect/1.png differ diff --git a/diagrams/2024/05/15/netlify-connect/diagram.yml b/diagrams/2024/05/15/netlify-connect/diagram.yml new file mode 100644 index 0000000..0c3b688 --- /dev/null +++ b/diagrams/2024/05/15/netlify-connect/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 + +# Required +name: "Netlify Connect" +images: + - 1.png +attribution: "https://docs.netlify.com/connect/get-started/?connect-data-source-type=contentful" +tags: + - cms + +# Optional +author: +description: | + With Netlify Connect, you can integrate content from multiple sources into a single data unification layer for easy access through a GraphQL API. Data updates sync automatically to ensure your sites and other web properties always have access to the latest content, all cached at the edge. \ No newline at end of file diff --git a/diagrams/2024/05/15/nginx/1.png b/diagrams/2024/05/15/nginx/1.png new file mode 100644 index 0000000..cc2dd81 Binary files /dev/null and b/diagrams/2024/05/15/nginx/1.png differ diff --git a/diagrams/2024/05/15/nginx/diagram.yml b/diagrams/2024/05/15/nginx/diagram.yml new file mode 100644 index 0000000..730f9fa --- /dev/null +++ b/diagrams/2024/05/15/nginx/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 + +# Required +name: "NGINX Management Suite" +images: + - 1.png +attribution: "https://docs.nginx.com/nginx-management-suite/acm/about/architecture/" +tags: + - web-server + +# Optional +author: +description: | + An overview of the NGINX Management Suite API Connectivity Manager architecture and personas. diff --git a/diagrams/2024/05/15/nomad/1.png b/diagrams/2024/05/15/nomad/1.png new file mode 100644 index 0000000..5486999 Binary files /dev/null and b/diagrams/2024/05/15/nomad/1.png differ diff --git a/diagrams/2024/05/15/nomad/diagram.yml b/diagrams/2024/05/15/nomad/diagram.yml new file mode 100644 index 0000000..09911a6 --- /dev/null +++ b/diagrams/2024/05/15/nomad/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 + +# Required +name: "Nomad architecture" +images: + - 1.png +attribution: "https://old-docs.nomad.xyz/dev/architecture.html" +tags: + - crypto + +# Optional +author: +description: | + Nomad is a new design for radically cheaper cross-chain communication without header verification. We expect operating Nomad to cut 90% of gas costs compared to a traditional header relay. To accomplish this, we took inspiration from optimistic systems (a la Optimistic Roll-ups). Nomad features many of the features we prize in an optimistic mechanism, like public verification, low gas fees, broad participation, but has a slightly different security model. + + Nomad will form the base layer of a cross-chain communication network that provides fast, cheap communication for all smart contract chains and rollups. It relies only on widely-available cryptographic primitives (unlike header relays), has a latency of thirty minutes (rather than an ORU’s one week latency), and imposes only about 120,000 gas overhead on message senders. diff --git a/diagrams/2024/05/15/prometheus/1.png b/diagrams/2024/05/15/prometheus/1.png new file mode 100644 index 0000000..1610bc0 Binary files /dev/null and b/diagrams/2024/05/15/prometheus/1.png differ diff --git a/diagrams/2024/05/15/prometheus/diagram.yml b/diagrams/2024/05/15/prometheus/diagram.yml new file mode 100644 index 0000000..73f41ee --- /dev/null +++ b/diagrams/2024/05/15/prometheus/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 + +# Required +name: "Prometheus architecture" +images: + - 1.png +attribution: "https://prometheus.io/docs/introduction/overview/" +tags: + - metrics + +# Optional +author: Julius Volz +description: | + Prometheus scrapes metrics from instrumented jobs, either directly or via an intermediary push gateway for short-lived jobs. It stores all scraped samples locally and runs rules over this data to either aggregate and record new time series from existing data or generate alerts. Grafana or other API consumers can be used to visualize the collected data. \ No newline at end of file diff --git a/diagrams/2024/05/15/self-hosted-retool-architecture/1.png b/diagrams/2024/05/15/self-hosted-retool-architecture/1.png new file mode 100644 index 0000000..e8c258a Binary files /dev/null and b/diagrams/2024/05/15/self-hosted-retool-architecture/1.png differ diff --git a/diagrams/2024/05/15/self-hosted-retool-architecture/diagram.yml b/diagrams/2024/05/15/self-hosted-retool-architecture/diagram.yml new file mode 100644 index 0000000..414e6dc --- /dev/null +++ b/diagrams/2024/05/15/self-hosted-retool-architecture/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 + +# Required +name: "Self-hosted Retool architecture" +images: + - 1.png +attribution: "https://docs.retool.com/self-hosted/concepts/architecture" +tags: + - deployment + +# Optional +author: +description: | + Organizations that have on-premise requirements can deploy the Retool platform on their own infrastructure. Each deployment instance uses a distributed set of containers with services for different functions. diff --git a/diagrams/2024/05/15/terraform/1.png b/diagrams/2024/05/15/terraform/1.png new file mode 100644 index 0000000..ed51f8e Binary files /dev/null and b/diagrams/2024/05/15/terraform/1.png differ diff --git a/diagrams/2024/05/15/terraform/diagram.yml b/diagrams/2024/05/15/terraform/diagram.yml new file mode 100644 index 0000000..cb30edb --- /dev/null +++ b/diagrams/2024/05/15/terraform/diagram.yml @@ -0,0 +1,15 @@ +schema-version: 0.1 + +# Required +name: "Terraform architecture" +images: + - 1.png +attribution: "https://spacelift.io/blog/terraform-architecture" +tags: + - iac + - infrastructure + +# Optional +author: Vivekanand Rapaka +description: | + An overview of Terraform, its objectives, fundamental architecture, and the workflow that encompasses the different stages of provisioning infrastructure with Terraform. diff --git a/diagrams/2024/05/16/flutter/1.png b/diagrams/2024/05/16/flutter/1.png new file mode 100644 index 0000000..207273f Binary files /dev/null and b/diagrams/2024/05/16/flutter/1.png differ diff --git a/diagrams/2024/05/16/flutter/2.png b/diagrams/2024/05/16/flutter/2.png new file mode 100644 index 0000000..4b9157b Binary files /dev/null and b/diagrams/2024/05/16/flutter/2.png differ diff --git a/diagrams/2024/05/16/flutter/3.png b/diagrams/2024/05/16/flutter/3.png new file mode 100644 index 0000000..148cf7b Binary files /dev/null and b/diagrams/2024/05/16/flutter/3.png differ diff --git a/diagrams/2024/05/16/flutter/4.png b/diagrams/2024/05/16/flutter/4.png new file mode 100644 index 0000000..9b1632c Binary files /dev/null and b/diagrams/2024/05/16/flutter/4.png differ diff --git a/diagrams/2024/05/16/flutter/diagram.yml b/diagrams/2024/05/16/flutter/diagram.yml new file mode 100644 index 0000000..18b9665 --- /dev/null +++ b/diagrams/2024/05/16/flutter/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 +# Required +name: Flutter Architectural Overview +images: + - 1.png + - 2.png + - 3.png + - 4.png +attribution: https://docs.flutter.dev/resources/architectural-overview +tags: + - ios + - android +# Optional +author: +description: | + Flutter is a cross-platform UI toolkit that is designed to allow code reuse across operating systems such as iOS and Android, while also allowing applications to interface directly with underlying platform services. The goal is to enable developers to deliver high-performance apps that feel natural on different platforms, embracing differences where they exist while sharing as much code as possible. diff --git a/diagrams/2024/05/16/open-health-stack/1.png b/diagrams/2024/05/16/open-health-stack/1.png new file mode 100644 index 0000000..d2ae5b9 Binary files /dev/null and b/diagrams/2024/05/16/open-health-stack/1.png differ diff --git a/diagrams/2024/05/16/open-health-stack/2.png b/diagrams/2024/05/16/open-health-stack/2.png new file mode 100644 index 0000000..7bc10a9 Binary files /dev/null and b/diagrams/2024/05/16/open-health-stack/2.png differ diff --git a/diagrams/2024/05/16/open-health-stack/3.png b/diagrams/2024/05/16/open-health-stack/3.png new file mode 100644 index 0000000..167a801 Binary files /dev/null and b/diagrams/2024/05/16/open-health-stack/3.png differ diff --git a/diagrams/2024/05/16/open-health-stack/4.png b/diagrams/2024/05/16/open-health-stack/4.png new file mode 100644 index 0000000..a415f43 Binary files /dev/null and b/diagrams/2024/05/16/open-health-stack/4.png differ diff --git a/diagrams/2024/05/16/open-health-stack/5.png b/diagrams/2024/05/16/open-health-stack/5.png new file mode 100644 index 0000000..ea3349c Binary files /dev/null and b/diagrams/2024/05/16/open-health-stack/5.png differ diff --git a/diagrams/2024/05/16/open-health-stack/diagram.yml b/diagrams/2024/05/16/open-health-stack/diagram.yml new file mode 100644 index 0000000..73783ba --- /dev/null +++ b/diagrams/2024/05/16/open-health-stack/diagram.yml @@ -0,0 +1,23 @@ +schema-version: 0.1 +# Required +name: Open Health Stack Use Cases +images: + - 1.png + - 2.png + - 3.png + - 4.png + - 5.png +attribution: https://developers.google.com/open-health-stack/use-cases +tags: + - android +# Optional +author: +description: |- + Open Health Stack provides building blocks for creating next-gen healthcare apps. + + OHS components make it easier to adopt FHIR. You can use them separately or combine them to form the foundation of an end-to-end digital health platform. + - FHIR-based Android apps + - Enhancing privacy, leveraging SMART-on-FHIR + - FHIR Analytics Solutions + - Foundations for an end-to-end digital health solution + - Hybrid Architecture Example diff --git a/diagrams/2024/05/16/ultralytics/1.png b/diagrams/2024/05/16/ultralytics/1.png new file mode 100644 index 0000000..0228f6a Binary files /dev/null and b/diagrams/2024/05/16/ultralytics/1.png differ diff --git a/diagrams/2024/05/16/ultralytics/diagram.yml b/diagrams/2024/05/16/ultralytics/diagram.yml new file mode 100644 index 0000000..b53c2ca --- /dev/null +++ b/diagrams/2024/05/16/ultralytics/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Ultralytics YOLOv5 Architecture +images: + - 1.png +attribution: https://docs.ultralytics.com/yolov5/tutorials/architecture_description/ +tags: + - computer-vision + - ai +# Optional +author: Glenn Jocher +description: | + YOLOv5 (v6.0/6.1) is a powerful object detection algorithm developed by Ultralytics. This article dives deep into the YOLOv5 architecture, data augmentation strategies, training methodologies, and loss computation techniques. This comprehensive understanding will help improve your practical application of object detection in various fields, including surveillance, autonomous vehicles, and image recognition. diff --git a/diagrams/2024/05/18/lichess/1.png b/diagrams/2024/05/18/lichess/1.png new file mode 100644 index 0000000..49e0f8a Binary files /dev/null and b/diagrams/2024/05/18/lichess/1.png differ diff --git a/diagrams/2024/05/18/lichess/2.png b/diagrams/2024/05/18/lichess/2.png new file mode 100644 index 0000000..0ab8e93 Binary files /dev/null and b/diagrams/2024/05/18/lichess/2.png differ diff --git a/diagrams/2024/05/18/lichess/diagram.yml b/diagrams/2024/05/18/lichess/diagram.yml new file mode 100644 index 0000000..8417e58 --- /dev/null +++ b/diagrams/2024/05/18/lichess/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Lichess architecture +images: + - 1.png + - 2.png +attribution: https://github.com/lichess-org/lila/tree/master?tab=readme-ov-file +tags: + - scala + - lucidchart +# Optional +author: Thibault Duplessis +description: | + Diagram of lichess architecture diff --git a/diagrams/2024/05/18/rabbit-mq/1.png b/diagrams/2024/05/18/rabbit-mq/1.png new file mode 100644 index 0000000..c399ba5 Binary files /dev/null and b/diagrams/2024/05/18/rabbit-mq/1.png differ diff --git a/diagrams/2024/05/18/rabbit-mq/diagram.yml b/diagrams/2024/05/18/rabbit-mq/diagram.yml new file mode 100644 index 0000000..dae399c --- /dev/null +++ b/diagrams/2024/05/18/rabbit-mq/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 +# Required +name: RabbitMQ architecture +images: + - 1.png +attribution: https://www.researchgate.net/publication/347866161_A_Fair_Comparison_of_Message_Queuing_Systems +tags: + - message-queue +# Optional +author: Guo Fu +description: | + In a RabbitMQ cluster, there can be two type of nodes,memory node and disk + node. There is at least one disk nodein the cluster, on which configuration + information and meta-information are stored. It should be noted that + RabbitMQ’sarchitecture has poor scalability due to the complete replica-tion + design. diff --git a/diagrams/2024/05/18/redux/1.png b/diagrams/2024/05/18/redux/1.png new file mode 100644 index 0000000..234aca9 Binary files /dev/null and b/diagrams/2024/05/18/redux/1.png differ diff --git a/diagrams/2024/05/18/redux/diagram.yml b/diagrams/2024/05/18/redux/diagram.yml new file mode 100644 index 0000000..11b666b --- /dev/null +++ b/diagrams/2024/05/18/redux/diagram.yml @@ -0,0 +1,16 @@ +schema-version: 0.1 +# Required +name: Redux data flow +images: + - 1.png +attribution: https://redux.js.org/tutorials/fundamentals/part-2-concepts-data-flow +tags: + - react + - frontend +# Optional +author: Mark Erikson +description: | + State describes the condition of the app at a specific point in time + The UI is rendered based on that state + When something happens (such as a user clicking a button), the state is updated based on what occurred + The UI re-renders based on the new state diff --git a/diagrams/2024/05/18/terraform-enterprise/1.avif b/diagrams/2024/05/18/terraform-enterprise/1.avif new file mode 100644 index 0000000..538a490 Binary files /dev/null and b/diagrams/2024/05/18/terraform-enterprise/1.avif differ diff --git a/diagrams/2024/05/18/terraform-enterprise/2.avif b/diagrams/2024/05/18/terraform-enterprise/2.avif new file mode 100644 index 0000000..5e2a712 Binary files /dev/null and b/diagrams/2024/05/18/terraform-enterprise/2.avif differ diff --git a/diagrams/2024/05/18/terraform-enterprise/diagram.yml b/diagrams/2024/05/18/terraform-enterprise/diagram.yml new file mode 100644 index 0000000..e6b49a8 --- /dev/null +++ b/diagrams/2024/05/18/terraform-enterprise/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Terraform Enterprise AWS architecture +images: + - 1.avif + - 2.avif +attribution: https://developer.hashicorp.com/terraform/enterprise/replicated/architecture/reference-architecture/aws +tags: + - terraform + - infrastructure + - enterprise +# Optional +author: Hashicorp Team +description: | + Terraform Enterprise can be installed and function in different implementation modes with increasing capability and complexity + + Standalone - The base architecture with a single application node that supports the standard implementation requirements for the platform. + Active/Active - This is an extension of Standalone mode that adds multiple active node capability that can expand horizontally to support larger and increasing execution loads. diff --git a/diagrams/2024/05/18/wii-u/1.png b/diagrams/2024/05/18/wii-u/1.png new file mode 100644 index 0000000..b4ed766 Binary files /dev/null and b/diagrams/2024/05/18/wii-u/1.png differ diff --git a/diagrams/2024/05/18/wii-u/2.png b/diagrams/2024/05/18/wii-u/2.png new file mode 100644 index 0000000..2d623f6 Binary files /dev/null and b/diagrams/2024/05/18/wii-u/2.png differ diff --git a/diagrams/2024/05/18/wii-u/3.png b/diagrams/2024/05/18/wii-u/3.png new file mode 100644 index 0000000..5ed0f68 Binary files /dev/null and b/diagrams/2024/05/18/wii-u/3.png differ diff --git a/diagrams/2024/05/18/wii-u/diagram.yml b/diagrams/2024/05/18/wii-u/diagram.yml new file mode 100644 index 0000000..2ee09b3 --- /dev/null +++ b/diagrams/2024/05/18/wii-u/diagram.yml @@ -0,0 +1,18 @@ +schema-version: 0.1 +# Required +name: Wii U architecture +images: + - 1.png + - 2.png +attribution: https://www.copetti.org/writings/consoles/wiiu/ +tags: + - scala + - lucidchart +# Optional +author: Rodrigo Copetti +description: | + The internal architecture of the GamePad. + + Overview of the GamePad-Wii U connection. + + Memory layout of general-purpose memory (in ‘Wii U’ mode). diff --git a/diagrams/2024/05/19/dbt/1.png b/diagrams/2024/05/19/dbt/1.png new file mode 100644 index 0000000..2577cf8 Binary files /dev/null and b/diagrams/2024/05/19/dbt/1.png differ diff --git a/diagrams/2024/05/19/dbt/diagram.yml b/diagrams/2024/05/19/dbt/diagram.yml new file mode 100644 index 0000000..2c571d2 --- /dev/null +++ b/diagrams/2024/05/19/dbt/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: dbt Cloud Architecture +images: + - 1.png +attribution: https://docs.getdbt.com/docs/cloud/about-cloud/architecture +tags: + - analytics +# Optional +author: klehmer +description: | + The dbt Cloud application has two types of components: static and dynamic. The static components are always running to serve highly available dbt Cloud functions, like the dbt Cloud web application. On the other hand, the dynamic components are created ad-hoc to handle tasks such as background jobs or requests to use the IDE. diff --git a/diagrams/2024/05/19/docusaurus/1.png b/diagrams/2024/05/19/docusaurus/1.png new file mode 100644 index 0000000..8896e75 Binary files /dev/null and b/diagrams/2024/05/19/docusaurus/1.png differ diff --git a/diagrams/2024/05/19/docusaurus/diagram.yml b/diagrams/2024/05/19/docusaurus/diagram.yml new file mode 100644 index 0000000..8cced41 --- /dev/null +++ b/diagrams/2024/05/19/docusaurus/diagram.yml @@ -0,0 +1,11 @@ +schema-version: 0.1 +# Required +name: Docusaurus Architecture +images: + - 1.png +attribution: https://docusaurus.io/docs/advanced/architecture +tags: + - documentation +# Optional +author: Joshua Chen +description: Docusaurus is a static-site generator. It builds a single-page application with fast client-side navigation, leveraging the full power of React to make your site interactive. It provides out-of-the-box documentation features but can be used to create any kind of site (personal website, product, blog, marketing landing pages, etc). diff --git a/diagrams/2024/05/19/excutorch/1.png b/diagrams/2024/05/19/excutorch/1.png new file mode 100644 index 0000000..d69e2aa Binary files /dev/null and b/diagrams/2024/05/19/excutorch/1.png differ diff --git a/diagrams/2024/05/19/excutorch/diagram.yml b/diagrams/2024/05/19/excutorch/diagram.yml new file mode 100644 index 0000000..d18f921 --- /dev/null +++ b/diagrams/2024/05/19/excutorch/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: ExecuTorch Architecture +images: + - 1.png +attribution: https://pytorch.org/executorch/stable/getting-started-architecture +tags: + - ai +# Optional +author: Svetlana Karslioglu +description: | + In order to target on-device AI with diverse hardware, critical power requirements, and realtime processing needs, a single monolithic solution is not practical. Instead, a modular, layered, and extendable architecture is desired. ExecuTorch defines a streamlined workflow to prepare (export, transformation, and compilation) and execute a PyTorch program, with opinionated out-of-the-box default components and well-defined entry points for customizations. This architecture greatly improves portability, allowing engineers to use a performant lightweight, cross-platform runtime that easily integrates into different devices and platforms. diff --git a/diagrams/2024/05/19/faiss/1.png b/diagrams/2024/05/19/faiss/1.png new file mode 100644 index 0000000..162ca2d Binary files /dev/null and b/diagrams/2024/05/19/faiss/1.png differ diff --git a/diagrams/2024/05/19/faiss/diagram.yml b/diagrams/2024/05/19/faiss/diagram.yml new file mode 100644 index 0000000..cdbb31a --- /dev/null +++ b/diagrams/2024/05/19/faiss/diagram.yml @@ -0,0 +1,12 @@ +schema-version: 0.1 +# Required +name: Faiss Architecture +images: + - 1.png +attribution: https://github.com/facebookresearch/faiss/wiki/Faiss-code-structure +tags: + - ai +# Optional +author: Matthijs Douze +description: | + Faiss is a library for efficient similarity search and clustering of dense vectors. It contains algorithms that search in sets of vectors of any size, up to ones that possibly do not fit in RAM. It also contains supporting code for evaluation and parameter tuning. Faiss is written in C++ with complete wrappers for Python/numpy. Some of the most useful algorithms are implemented on the GPU. It is developed primarily at Meta's Fundamental AI Research group. diff --git a/diagrams/2024/05/19/k8sgpt/1.png b/diagrams/2024/05/19/k8sgpt/1.png new file mode 100644 index 0000000..ddfcb8e Binary files /dev/null and b/diagrams/2024/05/19/k8sgpt/1.png differ diff --git a/diagrams/2024/05/19/k8sgpt/diagram.yml b/diagrams/2024/05/19/k8sgpt/diagram.yml new file mode 100644 index 0000000..36f4785 --- /dev/null +++ b/diagrams/2024/05/19/k8sgpt/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: K8sGPT Operator Architecture +images: + - 1.png +attribution: https://docs.k8sgpt.ai/reference/operator/overview/ +tags: + - kubernetes + - excalidraw +# Optional +author: Anais Urlichs +description: | + K8sGPT can run as a Kubernetes Operator inside the cluster. The scan results are provided as Kubernetes YAML manifests. diff --git a/diagrams/2024/05/19/knative-serving/1.png b/diagrams/2024/05/19/knative-serving/1.png new file mode 100644 index 0000000..984c3cb Binary files /dev/null and b/diagrams/2024/05/19/knative-serving/1.png differ diff --git a/diagrams/2024/05/19/knative-serving/2.png b/diagrams/2024/05/19/knative-serving/2.png new file mode 100644 index 0000000..5aa4a11 Binary files /dev/null and b/diagrams/2024/05/19/knative-serving/2.png differ diff --git a/diagrams/2024/05/19/knative-serving/diagram.yml b/diagrams/2024/05/19/knative-serving/diagram.yml new file mode 100644 index 0000000..5eb7a49 --- /dev/null +++ b/diagrams/2024/05/19/knative-serving/diagram.yml @@ -0,0 +1,14 @@ +schema-version: 0.1 +# Required +name: Knative Serving Architecture +images: + - 1.png + - 2.png +attribution: https://knative.dev/docs/serving/architecture/?spm=a2c65.11461447.0.0.2f4c27480jSkYE +tags: + - serverless-containers + - kubernetes + - drawio +# Optional +author: +description: Knative Serving consists of several components forming the backbone of the Serverless Platform. diff --git a/diagrams/2024/05/19/localai/1.png b/diagrams/2024/05/19/localai/1.png new file mode 100644 index 0000000..692c900 Binary files /dev/null and b/diagrams/2024/05/19/localai/1.png differ diff --git a/diagrams/2024/05/19/localai/diagram.yml b/diagrams/2024/05/19/localai/diagram.yml new file mode 100644 index 0000000..2cc71dd --- /dev/null +++ b/diagrams/2024/05/19/localai/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: LocalAI Architecture +images: + - 1.png +attribution: https://localai.io/docs/reference/architecture/ +tags: + - go + - ai +# Optional +author: Ettore Di Giacinto +description: | + LocalAI is an API written in Go that serves as an OpenAI shim, enabling software already developed with OpenAI SDKs to seamlessly integrate with LocalAI. It can be effortlessly implemented as a substitute, even on consumer-grade hardware. This capability is achieved by employing various C++ backends, including ggml, to perform inference on LLMs using both CPU and, if desired, GPU. Internally LocalAI backends are just gRPC server, indeed you can specify and build your own gRPC server and extend LocalAI in runtime as well. It is possible to specify external gRPC server and/or binaries that LocalAI will manage internally. diff --git a/diagrams/2024/05/19/scylladb/1.png b/diagrams/2024/05/19/scylladb/1.png new file mode 100644 index 0000000..3916047 Binary files /dev/null and b/diagrams/2024/05/19/scylladb/1.png differ diff --git a/diagrams/2024/05/19/scylladb/2.png b/diagrams/2024/05/19/scylladb/2.png new file mode 100644 index 0000000..4b4c8d4 Binary files /dev/null and b/diagrams/2024/05/19/scylladb/2.png differ diff --git a/diagrams/2024/05/19/scylladb/3.png b/diagrams/2024/05/19/scylladb/3.png new file mode 100644 index 0000000..d46c626 Binary files /dev/null and b/diagrams/2024/05/19/scylladb/3.png differ diff --git a/diagrams/2024/05/19/scylladb/4.png b/diagrams/2024/05/19/scylladb/4.png new file mode 100644 index 0000000..f37f0cb Binary files /dev/null and b/diagrams/2024/05/19/scylladb/4.png differ diff --git a/diagrams/2024/05/19/scylladb/5.png b/diagrams/2024/05/19/scylladb/5.png new file mode 100644 index 0000000..5a03116 Binary files /dev/null and b/diagrams/2024/05/19/scylladb/5.png differ diff --git a/diagrams/2024/05/19/scylladb/diagram.yml b/diagrams/2024/05/19/scylladb/diagram.yml new file mode 100644 index 0000000..ed46f41 --- /dev/null +++ b/diagrams/2024/05/19/scylladb/diagram.yml @@ -0,0 +1,17 @@ +schema-version: 0.1 +# Required +name: ScyllaDB Ring Architecture +images: + - 1.png + - 2.png + - 3.png + - 4.png + - 5.png +attribution: https://opensource.docs.scylladb.com/stable/architecture/ringarchitecture/index.html +tags: + - nosql + - cassandra +# Optional +author: Anna Stuchlik +description: | + Scylla is a database that scales out and up. Scylla adopted much of its distributed scale-out design from the Apache Cassandra project (which adopted distribution concepts from Amazon Dynamo and data modeling concepts from Google BigTable). diff --git a/diagrams/2024/05/19/steampipe/1.webp b/diagrams/2024/05/19/steampipe/1.webp new file mode 100644 index 0000000..dde426a Binary files /dev/null and b/diagrams/2024/05/19/steampipe/1.webp differ diff --git a/diagrams/2024/05/19/steampipe/diagram.yml b/diagrams/2024/05/19/steampipe/diagram.yml new file mode 100644 index 0000000..79dac1d --- /dev/null +++ b/diagrams/2024/05/19/steampipe/diagram.yml @@ -0,0 +1,13 @@ +schema-version: 0.1 +# Required +name: Steampipe Architecture +images: + - 1.webp +attribution: https://steampipe.io/docs/develop/overview +tags: + - database + - mermaid +# Optional +author: +description: | + Steampipe uses a Postgres Foreign Data Wrapper to present data from external systems and services as database tables. The Steampipe Foreign Data Wrapper (FDW) provides a Postgres extension that allows Postgres to connect to external data in a standardized way. The Steampipe FDW does not directly interface with external systems, but instead relies on plugins to implement the API/provider specific code and return it in a standard format via gRPC. This approach simplifies extending Steampipe as the Postgres-specific logic is encapsulated in the FDW, and API and service specific code resides only in the plugin. diff --git a/diagrams/2024/05/19/strapi/1.png b/diagrams/2024/05/19/strapi/1.png new file mode 100644 index 0000000..7cdfe99 Binary files /dev/null and b/diagrams/2024/05/19/strapi/1.png differ diff --git a/diagrams/2024/05/19/strapi/diagram.yml b/diagrams/2024/05/19/strapi/diagram.yml new file mode 100644 index 0000000..f17a4a8 --- /dev/null +++ b/diagrams/2024/05/19/strapi/diagram.yml @@ -0,0 +1,11 @@ +schema-version: 0.1 +# Required +name: Strapi Architecture +images: + - 1.png +attribution: https://strapi.io/blog/strapi-architecture +tags: + - cms +# Optional +author: Hana Khelifa +description: Strapi's architecture is decomposed into several independent but interconnected services. At its core, Strapi is built on a modern JavaScript stack, leveraging Node.js, Koa, and React, among other technologies. It also operates on a modular architecture that houses various registries, a dynamic plugin system, and an extensible API framework. diff --git a/docs/assets/banner.png b/docs/assets/banner.png new file mode 100644 index 0000000..5283492 Binary files /dev/null and b/docs/assets/banner.png differ diff --git a/featured/2024/05.yml b/featured/2024/05.yml new file mode 100644 index 0000000..75d45be --- /dev/null +++ b/featured/2024/05.yml @@ -0,0 +1,2 @@ +schema-version: 0.1 +diagram: 2024/05/12/acrolinx-platform diff --git a/make.sh b/make.sh new file mode 100755 index 0000000..1935fd7 --- /dev/null +++ b/make.sh @@ -0,0 +1,47 @@ +#!/bin/sh +set -eu +if [ ! -e "$(dirname "$0")/ci/sub/.git" ]; then + set -x + git submodule update --init + set +x +fi +. "$(dirname "$0")/ci/sub/lib.sh" +cd "$(dirname "$0")" + +_ensure_referenced_images() { + f="$1" + dir=$(dirname "$f") + imgs=$(yq eval '.images[]' "$f") + + if [ -z "$imgs" ]; then + echoerr "No images found in $f." + return 1 + fi + + exists=true + for img in $imgs; do + if [ ! -f "$dir/$img" ]; then + echoerr "The image file '$img' does not exist in the directory '$dir'." + exists=false + fi + done + if [ $exists == false ]; then + return 1 + fi +} + +ensure_referenced_images() { + sh_c XARGS_N=1 xargsd "'diagram\.\(yaml\|yml\)$'" | while IFS= read -r f; do + _ensure_referenced_images "$f" + done +} + +fmt_yaml() { + sh_c XARGS_N=1 xargsd "'\.\(yaml\|yml\)$'" yq eval -P -i +} + +ensure_changed_files +job_parseflags "$@" +runjob fmt fmt_yaml & +runjob imgcheck ensure_referenced_images & +ci_waitjobs