/explore
|
You are here 
|
wahibhaq.com | ||
| | | | |
sookocheff.com
Microservices have become part of the software engineering cultural zeitgeist to the extent that alternative approaches to architecture and development are treated as somehow inferior. Given the challenges that running microservices present, I usually recommend beginning development of new projects and systems as a single deployable unit - the monolith. Sam Newman, in the book "Building Microservices", agrees with this approach. He recommends leveraging microservices only if you can become convinced of the benefits for your system, not as a default for every project. |
|
| | | | | ||
| | | | |
blog.martinig.ch
Immature software developers, test coverage, software architecture decisions, product increment, Java interview, retrospectives tools and test data generators. |
|
| | | | | ||
| | | | |
benoitpasquier.com
To be sure new code won't break old one already implemented, it's best practice to write unit tests. When it comes to app architectures, it can be a challenge to write those tests. Following an MVVM pattern, how to unit test a view and its viewModel? That's what I would like to cover here using dependency injection. |
|
| | | | | ||
| | | | |
blog.theamazingrando.com
The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. |
|
| | | |||
