Boilerplate repository to showcase me (and others) my current way of building an AWS baked backend.
I can't really remember how I wrote code several years ago and why I did things in a certain way. With this repository I would like to capture all my (new) learnings in one central (or two?) place. I selected a simple theme "Todo list" to keep the scope as small as possible.
[...] Nothing in an inner circle can know anything at all about something in an outer circle. In particular, the name of something declared in an outer circle must not be mentioned by the code in the an inner circle. [...] > read full article
Holds functionality which could be used across all layers.
Holds the domain (behavior) logic of the application.
Holds the application use cases, how to interact with the application.
Holds the concrete implementation which are defined either in 1.domain or 2.application.
Holds the entry points to the application.
Holds the definition of the AWS infrastructure.
[...] Event Sourcing ensures that all changes to application state are stored as a sequence of events. [...] read full article
It's not part of the code, yet. As soon as it's available I will add a small description here.
From the fully automated CI/CD pipeline to the whole AWS infrastructure everything is written as code to have full visibility and reproducibility of the used infrastructure. Thanks to AWS CDK!
No one likes conflicts in code styles. No. One. Therefore I use (hopefully) the right mixture of three different tools and ensure they are applied even before hitting the repository (at least if the git hooks are not deactivated on purpose accidentally).
- using CQRS (Command Query Responsibility Segregation)
- tell me!