Explore >> Select a destination
|
You are here 
|
www.code4it.dev | ||
| | | | |
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. | |
| | | | |
herbertograca.com
|
|
| | | | | Documenting Software Architecture When we need to explain to someone else (new developer, product owner, investor, ...) how the application works, we need documentation. But what documentation options do we have that can express the whole application building blocks and how it works?! In this post I'm going to write about: - UML - 4+1... | |
| | | | |
blog.owulveryck.info
|
|
| | | | | Introduction C4 (Context, Containers, Components, and Code) is a powerful and flexible approach to visualizing software architectures. In a previous article I explained how I created a DSL to describe my C4 as data thanks to the CUE language. On Wardley's evolution axis the initial article was in stage I of evolution: making it work In this article, in a first part, we'll explore how I effectively use the C4 tool based on CUE to organize my code, handle tags, manage versioning, and integrate with Continu... | |
| | | | |
karthikkaranth.me
|
|
| | | An overview on how functions can implement interfaces in go | ||
