awesome-microfrontends
- https://github.com/ChristianUlbrich/awesome-microfrontends
- https://github.com/rajasegar/awesome-micro-frontends
Если кому мало на Английском:
- https://github.com/semlinker/awesome-micro-frontends
- https://github.com/ChristianUlbrich/awesome-microfrontends
- https://github.com/rajasegar/awesome-micro-frontends
Если кому мало на Английском:
- https://github.com/semlinker/awesome-micro-frontends
GitHub
GitHub - ChristianUlbrich/awesome-microfrontends: A curated list of resources about everything Micro Frontends
A curated list of resources about everything Micro Frontends - ChristianUlbrich/awesome-microfrontends
"The Difference Between a Story and a Task" by Mike Cohn
https://www.mountaingoatsoftware.com/blog/the-difference-between-a-story-and-a-task
Если кому некогда читать, то Ron Jeffries уже дал краткий "пересказ" 🙂:
📝 "the difference between a story and a task is like the difference between pants and underpants: only one of them is a public matter."
https://twitter.com/RonJeffries/status/1314273610148777985?s=19
#Agile
https://www.mountaingoatsoftware.com/blog/the-difference-between-a-story-and-a-task
Если кому некогда читать, то Ron Jeffries уже дал краткий "пересказ" 🙂:
📝 "the difference between a story and a task is like the difference between pants and underpants: only one of them is a public matter."
https://twitter.com/RonJeffries/status/1314273610148777985?s=19
#Agile
Mountain Goat Software
The Difference Between a Story and a Task
Here is the real difference between a story and a task in Scrum.
Тред заслуживает на прочтение:
Where does all this misunderstanding of CQRS and microservices and event sourcing come from?
https://twitter.com/jbogard/status/1315082571118710786?s=19
#DDD #Microservices
Where does all this misunderstanding of CQRS and microservices and event sourcing come from?
https://twitter.com/jbogard/status/1315082571118710786?s=19
#DDD #Microservices
Twitter
jimmybogard.usd 🇺🇦🍻
Where does all this misunderstanding of CQRS and microservices and event sourcing come from? reddit.com/r/microservice…
Архитектура ИТ-решений
Подарок для методиста https://microservice-api-patterns.org/ Обратите внимание на вводное слайд-шоу в верхнем правом углу
Twitter
Gregor
I have a well-known weakness for architecture icons, but these ones are especially nicely done: https://t.co/gDFOKE0Ixi Of course, there are some smart heads behind them, e.g. @pautasso, @uwe_zdun and the Twitter-shy Olaf Zimmermann. #apis #microservices…
На DotNext 2020 Moscow выступит Владимир Хориков (@vkhorikov) — эксперт и автор курсов по Domain Driven Design.
В своем докладе он разберет самые важные аспекты DDD и поможет глубже его понять.
Подробности и билеты: https://t.co/aojAA87L7C
https://dotnext-moscow.ru/2020/msk/talks/23lzgqtlrzsf5b23becvyn/
#DDD
В своем докладе он разберет самые важные аспекты DDD и поможет глубже его понять.
Подробности и билеты: https://t.co/aojAA87L7C
https://dotnext-moscow.ru/2020/msk/talks/23lzgqtlrzsf5b23becvyn/
#DDD
Analyzing the Limits of Connection Scalability in Postgres
https://www.citusdata.com/blog/2020/10/08/analyzing-connection-scalability/
#Database #PostgreSQL
https://www.citusdata.com/blog/2020/10/08/analyzing-connection-scalability/
#Database #PostgreSQL
Citus Data
Analyzing the Limits of Connection Scalability in Postgres
Postgres doesn’t handle large numbers of connections particularly well. This post explores why it’s important to improve connection scalability, followed by an analysis of the limiting aspects of Postgres connection scalability, from memory usage to snapshot…
emacsway-log: Software Design, Clean Architecture, DDD, Microservice Architecture, Distributed Systems, XP, Agile, etc.
В последнее время очень популярными стали обсуждения в стиле Agile vs. Architecture. Давайте посмотрим, что говорит по этому поводу Agile Manifesto. Некоторые из принципов Agile Manifesto ( https://agilemanifesto.org/principles.html ): 📝 "Изменение требований…
О стоимости изменения кода с точки зрения архитектуры - у Len Bass хорошо раскрывается эта тема в главе 7 Modifiability "Architecture in practice" 3d ed.
#Agile #SoftwareDesign #SoftwareArchitecture
#Agile #SoftwareDesign #SoftwareArchitecture
По поводу зарплат ИТ-специалистов в США (через VPN): https://www.bls.gov/oes/current/oes_nat.htm#15-0000
Калькулятор зарплат:
https://about.gitlab.com/handbook/people-group/global-compensation/calculator/
#Career
Калькулятор зарплат:
https://about.gitlab.com/handbook/people-group/global-compensation/calculator/
#Career
Bureau of Labor Statistics
Occupational Employment and Wage Statistics (OEWS) Tables
Tables Created by BLS
Monorepo vs. polyrepo
https://github.com/joelparkerhenderson/monorepo_vs_polyrepo
P.S.: часто обсуждаемая тема в архитектурных кругах.
#SoftwareArchitecture
https://github.com/joelparkerhenderson/monorepo_vs_polyrepo
P.S.: часто обсуждаемая тема в архитектурных кругах.
#SoftwareArchitecture
GitHub
GitHub - joelparkerhenderson/monorepo-vs-polyrepo: Monorepo vs. polyrepo: architecture for source code management (SCM) version…
Monorepo vs. polyrepo: architecture for source code management (SCM) version control systems (VCS) - joelparkerhenderson/monorepo-vs-polyrepo
Forwarded from Архитектура ИТ-решений
Талант Кента Бека - автора экстремального программирования (XP), заключается в формулировании едва осознаваемых вещей понятными и простыми словами. Его очередная заметка: https://medium.com/@kentbeck_7670/monolith-services-theory-practice-617e4546a879
Medium
Monolith -> Services: Theory & Practice
How can we get from a monolith to micro-services quickly?
Все перечисленные по ссылке книги доступны для скачивания: https://postgrespro.ru/education/books
Достойное чтиво (особенно последняя). Дает комплексные знания в лаконичной форме.
#Database #PostgreSQL
Достойное чтиво (особенно последняя). Дает комплексные знания в лаконичной форме.
#Database #PostgreSQL
postgrespro.ru
Книги
Postgres Professional - российская компания, разработчик систем управления базами данных
Архитектура ИТ-решений
Талант Кента Бека - автора экстремального программирования (XP), заключается в формулировании едва осознаваемых вещей понятными и простыми словами. Его очередная заметка: https://medium.com/@kentbeck_7670/monolith-services-theory-practice-617e4546a879
Это нужно выделить отдельно. Более простого объяснения более важных вещей в IT-индустрии я пока еще не встречал:
📝 "These were elucidated in the mid-70s by Yourdon & Constantine in "Structured Design" https://amzn.to/2GsuXvQ and haven’t changed.
Their argument goes like this:
1. We design software to reduce its cost.
2. The cost of software is ≈ the cost of changing the software.
3. The cost of changing the software is ≈ the cost of the expensive changes (power laws and all that).
4. The cost of the expensive changes is generated by cascading changes — if I change this then I have to change that and that, and if I change that then…
5. Coupling between elements of a design is this propensity for a change to propagate.
6. So, design ≈ cost ≈ change ≈ big change ≈ coupling. Transitively, software design ≈ managing coupling.
(This skips loads of interesting stuff, but I’m just trying to set up the argument for why rapid decomposition of a monolith into micro-services is counter-productive.)"
- "Monolith -> Services: Theory & Practice" by Kent Beck
https://medium.com/@kentbeck_7670/monolith-services-theory-practice-617e4546a879
📝 "These were elucidated in the mid-70s by Yourdon & Constantine in "Structured Design" https://amzn.to/2GsuXvQ and haven’t changed.
Their argument goes like this:
1. We design software to reduce its cost.
2. The cost of software is ≈ the cost of changing the software.
3. The cost of changing the software is ≈ the cost of the expensive changes (power laws and all that).
4. The cost of the expensive changes is generated by cascading changes — if I change this then I have to change that and that, and if I change that then…
5. Coupling between elements of a design is this propensity for a change to propagate.
6. So, design ≈ cost ≈ change ≈ big change ≈ coupling. Transitively, software design ≈ managing coupling.
(This skips loads of interesting stuff, but I’m just trying to set up the argument for why rapid decomposition of a monolith into micro-services is counter-productive.)"
- "Monolith -> Services: Theory & Practice" by Kent Beck
https://medium.com/@kentbeck_7670/monolith-services-theory-practice-617e4546a879
emacsway-log: Software Design, Clean Architecture, DDD, Microservice Architecture, Distributed Systems, XP, Agile, etc.
А это, я так понимаю, - первоисточник и исходный код этой шпаргалки. Коммитил Nick Tune. EventStorming Glossary & Cheat sheet https://github.com/ddd-crew/eventstorming-glossary-cheat-sheet И канонический адрес: https://ddd-crew.github.io/eventstorming-glossary…
Еще одна хорошая "шпаргалка"
Open Agile Architecture : 19. Event Storming
- https://pubs.opengroup.org/architecture/o-aa-standard/#event-storming-workshop
#DDD #EventStorming
Open Agile Architecture : 19. Event Storming
- https://pubs.opengroup.org/architecture/o-aa-standard/#event-storming-workshop
#DDD #EventStorming
Просто превосходный краткий материал по проектированию микросервисов:
"Building microservices on Azure"
- https://docs.microsoft.com/en-us/azure/architecture/microservices/
Особенно это:
- "Using domain analysis to model microservices" https://docs.microsoft.com/en-us/azure/architecture/microservices/model/domain-analysis
и это:
- "Identifying microservice boundaries" https://docs.microsoft.com/en-us/azure/architecture/microservices/model/microservice-boundaries
#DDD #Microservices
"Building microservices on Azure"
- https://docs.microsoft.com/en-us/azure/architecture/microservices/
Особенно это:
- "Using domain analysis to model microservices" https://docs.microsoft.com/en-us/azure/architecture/microservices/model/domain-analysis
и это:
- "Identifying microservice boundaries" https://docs.microsoft.com/en-us/azure/architecture/microservices/model/microservice-boundaries
#DDD #Microservices
Docs
Microservices Architecture Style - Azure Architecture Center
Learn about microservices on Azure. This architectural style builds applications that are resilient, highly scalable, and independently deployable.
Свеженькая статья на острую тему - " Are We Really Bad at Estimating?" by Mike Cohn:
- https://www.mountaingoatsoftware.com/blog/are-we-really-bad-at-estimating
Там есть ссылка на вот такой любопытный файлик (содержание которого уже не ново, но дает еще один угол зрения) - "Uncertainty Intervals versus Interval Uncertainty: An Alternative Method for Eliciting Effort Prediction Intervalsin Software Development Projects" by Jørgensen, M., Simula Research Laboratory:
- https://www.simula.no/sites/default/files/publications/files/promac-final2.pdf
#Agile
- https://www.mountaingoatsoftware.com/blog/are-we-really-bad-at-estimating
Там есть ссылка на вот такой любопытный файлик (содержание которого уже не ново, но дает еще один угол зрения) - "Uncertainty Intervals versus Interval Uncertainty: An Alternative Method for Eliciting Effort Prediction Intervalsin Software Development Projects" by Jørgensen, M., Simula Research Laboratory:
- https://www.simula.no/sites/default/files/publications/files/promac-final2.pdf
#Agile
Mountain Goat Software
Better Estimates Are Possible on Agile Teams
Studies have shown how we are - and are not - good at estimation, and what can be done to improve our accuracy.