Collection of various links – blogs, articles, libraries/frameworks & repos, etc. Not necessarily really awesome.
Last active
February 21, 2022 09:29
-
-
Save vhenzl/37e64eca26d501df6e3324789d5b0a7f to your computer and use it in GitHub Desktop.
Awesome whatever (PHP, DDD, CQRS, events & messaging, Doctrine, REST & APIs, PHPStorm,... links)
- User Stories: A Foundation for UI Design
- Everything You Wanted to Know About User Stories (But Were Afraid to Ask)
- Bill Wake: INVEST in Good Stories, and SMART Tasks - the original description of INVEST
- Bill Wake: Twenty Ways to Split Stories
- 10 useful strategies for breaking down large User Stories (and a cheatsheet)
- Richard Lawrence: How to Split a User Story
- Splitting User Stories - alternative explanation of INVEST
- SAFe - Story
- When is a User Story “Done?”— Acceptance Criteria and the Definition of “Done”
- User stories: a beginner’s guide to acceptance criteria
- On Acceptance criteria for user stories
- Richard Lawrence: Growing DONE—How to Make the Definition of Done Work for Your Team
- How to Write User Story Acceptance Criteria
- Speaker Deck: A Monorepo vs Manyrepos by Fabien Potencier
- Benjamin Eberlei: Monorepos - Working with a single, big, scary version control repository (PDF)
- Benjamin Eberlei, Whitewashing: Monolithic Repositories with PHP and Composer
- Benjamin Eberlei, Whitewashing: Composer Monorepo Plugin (previously called Fiddler)
- beberlei/composer-monorepo-plugin - Integrates Composer into monolithic repositories with many packages
- theofidry/composer-inheritance-plugin - Opinionated version of Wikimedia composer-merge-plugin to work in pair with Bamarni composer-bin-plugin
- Composer repositories - path
- splitsh/lite - Split your monorepo into many repos
- vhenzl/MarsRover
See also REST & CQRS
- .NET Junkie: Meanwhile... on the command side of my architecture
- .NET Junkie: Meanwhile... on the query side of my architecture
If you find yourself in a situation that you have multiple command handlers that share the same logic, either extract that logic to an aggregate service (http://blog.ploeh.dk/2010/02/02/RefactoringtoAggregateServices/) or start publishing domain events. – Steven aka .NET Junkie, 29/11/2014
- Glossary of Domain-Driven Design Terms
- Martin Fowler: Bounded Context
- Martin Fowler: DDD Aggregate
- Domain Language: DDD Reference
- Vaughn Vernon (blog)
- Jimmy Bogard: 10 Lessons from a Long Running DDD Project – Part 1
- Jimmy Bogard: 10 Lessons from a Long Running DDD Project – Part 2
- Jan Kuchař: Event-Sourcing basic example app – Learning DDD
- Rob Allen: Designing the M in MVC
- Mastering Symfony2 Performance – Doctrine
- 5 Doctrine ORM Performance Traps You Should Avoid
- Ross Tuck: Persisting Value Objects in Doctrine
- Filtering Associations with Doctrine 2
- Benjamin Eberlei – Whitewashing: On Taming Repository Classes in Doctrine (criteria/specifications)
- Ocramius: Doctrine ORM Hydration Performance Optimization
- Value Objects, Immutable objects and Doctrine Embeddables (google cache)
- Knp University: Go Pro with Doctrine Queries
- TomasVotruba/awesome-doctrine
- Udi Dahan: Domain Events – Salvation
- Jimmy Bogard: A better domain events pattern
- Martin Fowler: EAA – Domain Event
- Ben Foster: Deferred Domain Events
- Tony Truong: Domain Events Pattern Example (C#)
- Marc Costello: Using Domain Events (C#)
- Jayway Tech blog: Don't publish Domain Events, return them! (Java)
- Domain Event - The Hidden Gem of DDD (PHP)
- Our experience with Domain Events (PHP)
- Mathias Verraes: Domain Events
- Mathias Verraes: Messaging Flavours
- InfoQ: Domain Events and Eventual Consistency
- Florin Preda – Reflective Software: Eventual Consistency via Domain Events and Azure Service Bus
- Vaughn Vernon: Implementing Domain-Driven Design: Aggregates – Rule: Use Eventual Consistency Outside the Boundary
- Visual Studio Magazine: Simplifying Applications by Implementing Eventual Consistency with Domain Events
- MSDN magazine: Cutting Edge: Documents, Databases and Eventual Consistency
- Jimmy Bogard: Eventual consistency, CQRS and interaction design
- Using HTTP Methods for RESTful Services
- 10 Best Practices for Better RESTful API
- Best Practices for Designing a Pragmatic RESTful API
- REST API Design - Resource Modeling
- SO: What about actions that don't fit into the world of CRUD operations?
- RESTful API Design: simplify associations, sweep complexities under the HTTP ? (series)
- Stopařův průvodce REST API (CS)
- ploeh blog - REST
- MuleSoft: API Best Practices: Plan Your API
- SO: Creating one-to-one RESTful API relationship
- Jimmy Bogard: Entities aren’t resources, resources aren’t representations
- Jimmy Bogard: CQRS and REST: the perfect match
- Gabriel Schenker: CQRS applied
- InfoQ: Exposing CQRS Through a RESTful API
- SO: How to support Command in REST while doing REST, CQRS and EventSourcing together?
- Cqrs api v2 (slides 23-35)
- Wikipedia: HATEOAS
- Hateoas (willdurand/Hateoas documentation)
- MuleSoft: API Best Practices: Hypermedia (Part 1)
- Kevin Sookocheff: On choosing a hypermedia type for your API…
- MuleSoft: API Best Practices: Hypermedia (Part 3)
- Hypermedia Types: H Factor
- kevinswiber/siren - Siren: a hypermedia specification for representing entities
- JSON Schema – describes your JSON data format
- Schema.org – schemas for structured data on the Internet
- API Commons – collaborative design of API specifications, interfaces and data models
- JSONSchema.Net – generates JSON schema from JSON
- RAML
- API Blueprint
- Swagger
- Top Specification Formats for REST APIs (SEPTEMBER 8, 2015)
- Modeling Web APIs: your best choices (29/12/2015)
- REST API Documentation Part 2 (Feb. 02, 16)
- raml-org/raml-spec
- raml-org/raml-examples
- RAML APIs - A Collection of Popular REST APIs Described using RAML
- OAI/OpenAPI-Specification #476 - Interest in a JSON API-conformant example specification? (JSON:API)
- OAI/OpenAPI-Specification #519 - Ability to define generic wrapper around the output (JSON:API)
- OAI/OpenAPI-Specification #613 - Traits or Mixins
- Packagist - hateoas
- PHPPackages - hateoas()
- klimesf/nette-hateoas
- willdurand/Hateoas
- api-platform/api-platform (API-first web framework on top of Symfony with JSON-LD, Schema.org and Hydra support)
- The problems with Swagger
- Swagger, the REST Kryptonite
- The value proposition of Hypermedia
- REST lesson learned: Avoid hackable URLs
- REST efficiency
- REST lesson learned: Consider a self link on all resources
- Best Practices for Designing a Pragmatic RESTful API
- Should RESTful API's Include Relationships
- REST contract-first: Swagger & Gradle (CS)
- apigee: Web API Design – Crafting Interfaces that Developers Love (PDF)
- Loïc Faugeron: phpspec
- Marcello Duarte: My top ten favourite PHPSPEC limitations
- Getting Started With Phpspec
- PhpStorm & phpspec
- mrtnzlml/testbench
- Martin Zlámal: Jednoduché testování pro úplně každého
- Martin Zlámal: Testování presenterů v Nette
- Martin Zlámal: Testbench 2.3 is out (finally)
- mrtnzlml/testbench
- Jiří Pudil: Bootstrap your integration testing database
- Nette Tester – enjoyable unit testing
- Nette blog: tester
- phpFashion: Velestručné testování presenterů v Nette
- Behat: Quick start
- Eric Elliott: 5 Questions Every Unit Test Must Answer - How to Write Better Tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment