├── LICENSE └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Useful Microservices Reading List 2 | 3 | > **We don't need more useless `awesome lists`. We need useful reading lists that help us learn various practical aspects about a topic.** 4 | 5 | This repository has list of articles and videos that cover practical aspects of Microservices. It is not your just another awesome list. Its main purpose is to be useful rather than just another stupid list. 6 | 7 | ## Monolith first 8 | 9 | 1. :memo: Monolith First - [Link](https://martinfowler.com/bliki/MonolithFirst.html) 10 | 3. :memo: In Defence of the Monolith, [Link 1](https://www.infoq.com/articles/monolith-defense-part-1/) and [Link 2](https://www.infoq.com/articles/monolith-defense-part-2/) 11 | 4. :memo: The Death of Microservice Madness in 2018 - [Link](https://dwmkerr.com/the-death-of-microservice-madness-in-2018/) 12 | 5. :video_camera: Majestic Modular Monoliths - [Link](https://vimeo.com/233980163) 13 | 5. :memo: The Majestic Monolith - [Link](https://m.signalvnoise.com/the-majestic-monolith/) 14 | 6. :memo: About When Not to Do Microservices - [Link](https://blog.christianposta.com/microservices/when-not-to-do-microservices/) 15 | 7. :memo: Modules vs. microservices - [Link](https://www.oreilly.com/radar/modules-vs-microservices/) 16 | 8. :memo: Microservices Last Resort - [Link](https://www.theregister.com/2020/03/04/microservices_last_resort) 17 | 18 | ## When and Why Microservices? 19 | 20 | 1. :memo: Microservice Prerequisites - [Link](https://martinfowler.com/bliki/MicroservicePrerequisites.html) 21 | 3. :memo: Microservices Architecture Guidelines - [Link](https://github.com/justinamiller/Microservices-Architecture-Guidelines) 22 | 3. :memo: Microservices: To Do or Not to Do - LInk - [Link](http://www.bestdevops.com/microservices-to-do-or-not-to-do/) 23 | 4. :memo: Microservices — architecture nihilism in minimalism's clothes - [Link](https://vlfig.me/posts/microservices) 24 | 5. :video_camera: Microservices by Martin Fowler - [Link](https://www.youtube.com/watch?v=wgdBVIX9ifA) 25 | 26 | ## Should it be a Microservice? 27 | 28 | 1. :memo: Should that be a Microservice? Keep These Six Factors in Mind - [Link](https://tanzu.vmware.com/content/blog/should-that-be-a-microservice-keep-these-six-factors-in-mind) 29 | 30 | ## Mono-repo vs Repo per service 31 | 32 | 1. :memo: Advantages of monorepos - [Link](https://danluu.com/monorepo/) 33 | 2. :memo: Monorepos: Please don’t! - [Link](https://medium.com/@mattklein123/monorepos-please-dont-e9a279be011b) 34 | 3. :video_camera: Attack of the Monorepos - [Link](https://www.infoq.com/presentations/monorepos/) 35 | 4. :memo: Put your Microservices in a Monorepo - [Link](https://blog.upcoding.fr/microservices-in-a-monorepo/) 36 | 37 | ## Patterns 38 | 39 | 1. :memo: Communication in a microservice architecture - [Link](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/communication-in-microservice-architecture) 40 | 2. :memo: On Pass-through services - [Link](https://shekhargulati.com/2021/09/09/why-is-it-ok-to-write-pass-through-services-in-a-microservices-architecture/) 41 | 42 | ## Shared libraries 43 | 44 | 1. :memo: Why “Don’t Use Shared Libraries in Microservices” is Bad Advice - [Link](https://www.grahamlea.com/2016/04/shared-libraries-in-microservices-bad-advice/) 45 | 46 | ## Data Consistency 47 | 48 | 2. :memo: Data consistency in microservices architecture - [Link](https://ebaytech.berlin/data-consistency-in-microservices-architecture-bf99ba31636f) 49 | 3. :video_camera: Managing Data in Microservices - [Link](https://www.infoq.com/presentations/microservices-managing-data/) 50 | 3. :memo: Airbnb: Avoiding Double Payments in a Distributed Payments System - [Link](https://medium.com/airbnb-engineering/avoiding-double-payments-in-a-distributed-payments-system-2981f6b070bb) 51 | 52 | ## DDD and CQRS 53 | 54 | 1. :memo: Tackle Business Complexity in a Microservice with DDD and CQRS Patterns - [Link](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/) 55 | 2. :memo: Core Domain Patterns - [Link](https://medium.com/nick-tune-tech-strategy-blog/core-domain-patterns-941f89446af5) 56 | 3. :memo: Datomic: Event Sourcing without the hassle - [Link](https://vvvvalvalval.github.io/posts/2018-11-12-datomic-event-sourcing-without-the-hassle.html) 57 | 58 | ## Caching 59 | 60 | 1. :memo: Caching strategies - [Link](https://zubialevich.blogspot.com/2018/08/caching-strategies.html) 61 | 2. :memo: Blazing Fast Data Lookup in a Microservices World - [Link](https://medium.com/capital-one-tech/blazing-fast-data-lookup-in-a-microservices-world-dd3ae548ca45) 62 | 63 | ## Testing 64 | 65 | 1. :memo: Airbnb: Building an Effective Test Pipeline in a Service Oriented World - [Link](https://medium.com/airbnb-engineering/building-an-effective-test-pipeline-in-a-service-oriented-world-6968c513c6bd) 66 | 2. :memo: Testing in Production, the safe way - [Link](https://medium.com/@copyconstruct/testing-in-production-the-safe-way-18ca102d0ef1) 67 | 68 | ## Platform 69 | 70 | 1. :memo: Checklist: what had to be done before deploying microservices to production - [Link](https://habr.com/en/post/438186/) 71 | 2. :memo: Why you need a microservices management platform and how to build it - [Link](https://blog.griddynamics.com/build-a-microservices-platform-for-replatforming/) 72 | 73 | 74 | ## Network, Proxies, and Service Mesh 75 | 76 | 1. :memo: Introduction to modern network load balancing and proxying - [Link](https://blog.envoyproxy.io/introduction-to-modern-network-load-balancing-and-proxying-a57f6ff80236) 77 | 2. :memo: The evolution of L7, proxies, and microservices - [Link](https://blog.getambassador.io/the-evolution-of-l7-proxies-and-microservices-264381945f7d) 78 | 3. :memo: How we migrated Dropbox from Nginx to Envoy - [Link](https://dropbox.tech/infrastructure/how-we-migrated-dropbox-from-nginx-to-envoy) 79 | 4. :memo: Everything We Learned Running Istio In Production - [Link](https://engineering.hellofresh.com/everything-we-learned-running-istio-in-production-part-1-51efec69df65) 80 | 81 | ## Security 82 | 83 | 1. :video_camera: Security and Microservices - [Link](https://www.youtube.com/watch?v=ZXGaC3GR3zU) 84 | 2. :video_camera: Practical Microservice Security - [Link](https://www.youtube.com/watch?v=CseYwoLjBb0) 85 | 3. :video_camera: Top 10 Security Best Practices to secure your Microservices - [Link](https://www.youtube.com/watch?v=VtUQINsYXDM) 86 | 87 | ## Observability 88 | 89 | 1. :memo: Distributed Tracing — we’ve been doing it wrong - [Link](https://medium.com/@copyconstruct/distributed-tracing-weve-been-doing-it-wrong-39fc92a857df) 90 | 2. :memo: Tracing at Slack: Thinking in Causal Graphs - [Link](https://slack.engineering/tracing-at-slack-thinking-in-causal-graphs/) 91 | 92 | ## Microservices Governance 93 | 94 | 1. :memo: Microservices Technical Governance - [Link](https://medium.com/ibm-garage/microservices-technical-governance-f5aed10189d1) 95 | 96 | ## Monolithic to Microservices 97 | 98 | 1. :memo: Shopify: Deconstructing the Monolith: Designing Software that Maximizes Developer Productivity - [Link](https://engineering.shopify.com/blogs/engineering/deconstructing-monolith-designing-software-maximizes-developer-productivity) 99 | 2. :video_camera: Monolith Decomposition Patterns - [Link](https://www.infoq.com/presentations/microservices-principles-patterns/) 100 | 3. :memo: 3 Strategies for implementing a microservices architecture - [Link](https://about.gitlab.com/blog/2019/06/17/strategies-microservices-architecture/) 101 | 4. :memo: Untangling Microservices, or Balancing Complexity in Distributed Systems - [Link](https://vladikk.com/2020/04/09/untangling-microservices/) 102 | 5. :memo: GitHub’s Journey from Monolith to Microservices - [Link](https://www.infoq.com/articles/github-monolith-microservices/) 103 | 104 | 105 | ## Microservices to Monolithic 106 | 107 | 1. :memo: Istio as an Example of When Not to Do Microservices - [Link](https://blog.christianposta.com/microservices/istio-as-an-example-of-when-not-to-do-microservices/) 108 | 2. :video_camera: To Microservices and Back Again - [Link](https://www.infoq.com/presentations/microservices-monolith-antipatterns/) 109 | 110 | 111 | ## People 112 | 113 | 1. :memo: Forget monoliths vs. microservices. Cognitive load is what matters. - [Link](https://techbeacon.com/app-dev-testing/forget-monoliths-vs-microservices-cognitive-load-what-matters) 114 | 2. :video_camera: Monoliths vs Microservices is Missing the Point—Start with Team Cognitive Load - [Link](https://www.youtube.com/watch?v=haejb5rzKsM) 115 | 116 | ## Microservices Survey 117 | 118 | 1. :book: State Of Microservices 2020 - [Link](https://tsh.io/state-of-microservices/) 119 | 120 | 121 | ## Real world Microservices architecture 122 | 123 | 1. :memo: Microservice Architecture at Netflix - [Link](https://www.nginx.com/blog/microservices-at-netflix-architectural-best-practices/) 124 | 2. :memo: Microservice Architecture at Medium - [Link](https://medium.engineering/microservice-architecture-at-medium-9c33805eb74f) 125 | 3. :memo: Microservice Architecture at Uber - [Link 1](https://eng.uber.com/service-oriented-architecture/) and [Link 2](https://eng.uber.com/microservice-architecture/) 126 | 4. :memo: Microservice Architecture at Twitter - [Link 1](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2020/building-twitters-ad-platform-architecture-for-the-future.html), [Link 2](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2020/rebuild_twitter_public_api_2020.html), and [Link 3](https://blog.twitter.com/engineering/en_us/topics/infrastructure/2017/the-infrastructure-behind-twitter-scale.html) 127 | 5. :memo: Microservice Architecture at Amazon - [Link](http://highscalability.com/amazon-architecture) 128 | 6. :memo: Microservice Architecture at Airbnb - [Link 1](https://medium.com/airbnb-engineering/building-services-at-airbnb-part-1-c4c1d8fa811b) and [Link 2](https://medium.com/airbnb-engineering/building-services-at-airbnb-part-3-ac6d4972fc2d) 129 | 7. :memo: Microservice Architecture at Zolando - [Link](https://www.infoq.com/news/2016/02/Monolith-Microservices-Zalando/) 130 | 131 | ## Microservices Anti-patterns and Pitfalls 132 | 133 | 1. :memo: Microservices antipatterns and pitfalls - [Link](https://www.oreilly.com/content/microservices-antipatterns-and-pitfalls/) 134 | 2. :memo: 11 Reasons Why You Are Going To Fail With Microservices - [Link](https://medium.com/xebia-engineering/11-reasons-why-you-are-going-to-fail-with-microservices-29b93876268b) 135 | 3. :video_camera: To Microservices and Back Again - [Link](https://www.infoq.com/presentations/microservices-monolith-antipatterns/) 136 | 4. :memo: Microservices pitfalls - [Link](https://natalian.org/2019/05/16/Microservices_pitfalls/) 137 | 5. :memo: Why I stopped using Microservices - [Link](https://www.robinwieruch.de/microservices-tradeoffs) 138 | 6. :memo: Seven Microservices Anti-patterns - [Link](https://www.infoq.com/articles/seven-uservices-antipatterns/) 139 | --------------------------------------------------------------------------------