Hexagonal architecture (software) - Wikipedia

Core library for the Ruby flavour of Cucumber. Contribute to cucumber/cucumber-ruby-core development by creating an account on GitHub.

Website of Soenke Ruempler

In the last post, I talked about various architectures used as alternatives to MVC, in a attempt to solve MVCs problems, such as Massive View Controller. In this post, I would like to introduce you to another architecture, which seems to me to be the best starting point for your app’s architecture: the Clean Architecture. I think I first ran into the Clean Architecture in one of Uncle Bob’s presentations on YouTube. At first, I kind of wrote it off as a typical Java over-engineered design pattern. It wasn’t until earlier this year, probably years later after my initial discovery, that I ran into it again. I was looking for a better app architecture after an experience working for a large company with a large iOS team (with about 11 developers) and all the issues they had getting the app to work and test it. I kind of became obsessed with figuring out how to make an app easier to test. I searched the internet for app architectures and studied them. It took me awhile to get my head around the Clean Architecture, but once I did, I decided it would be my starting point for an app architecture.

Modular monoliths are simple(r) but not easy.

Most developers are aware of SOLID at this point, and 'I' stands for 'Interface Segregation Principle'. And like a lot of the other principles in SOLID, it has been wildly misunderstood.

Narrow integration tests are tests that only involve very few components, mostly relying on test doubles to simulate external dependencies. As always, we have Martin Fowler to thank for yet another excellent article on integration tests so I’ll simply refer to that for the details of what a narrow integration test is. That said, during 2019 I have grown increasingly convinced that the distinction between a narrow and wide integration (also know as system tests or end-to-end tests) is an important one, for two reasons:

This is my review of Clean Architecture by Uncle Bob. The book is undoubtedly a classic and I feel bad for not having read it earlier. I think it might have ...

A software engineer website

In this post, we'll look at how to apply the principles of The Clean Architecture to build a Xamarin.Forms Android app. This app will be based on a robust architecture that is loosely coupled and cleanly separates the important business or domain logic from other details and infrastructure like databases, UI frameworks, and network communications.

A simple way to encode dependency injection using the Reader monad and objects in OCaml (to work well with type inference).

25 October 2019 by Phillip Johnston • Last updated 9 September 2024Design patterns are valuable concepts to add to your mental library. These are non-obvious solutions to scenarios and problems frequently encountered in the programming world. Exposure to patterns shows you how many of your problems have been previously solved by others, freeing you to … Continue reading "Design Pattern Catalogue"

Let's treat JavaScript and browsers as flaky infrastructure, and act accordingly

In this episode, we’ll take a look at redesigning an API that has been developed in a traditional layered way, moving to a more interesting onion/hexagonal/ports and adapters architecture (which is apparently very fashionable right now in .NET land).

I’ve been trying to flee the over-engineered C# solution structures, with multiple projects, with related code scattered around. Even if an imperfect solution, I’ve turned to NetArchTest to help in guide on following some conventions in a simplified solution structure.

While Deptrac is commonly used to enforce horizontal boundaries within PHP projects, it can also help define and maintain vertical boundaries (such as Bounded Contexts in DDD speak, or Quanta) in PHP

A tutorial on building an Android wavetable synthesizer from scratch using Compose UI, Oboe library, and modern architecture guidelines.

<p>When writing tests, we do not want to hit the external API each time we run our tests. If we are coming from a dynamic language, such as Node.JS, we may want to a solution like <a href="https://www.npmjs.com/package/fetch-mock">fetch-mock</a> which will patch the implementation of <code>fetch</code> at runtime. This is not practical in Rust. There are some attempts, like the <a href="https://github.com/Shizcow/hotpatch">hotpatch</a> crate, but we will use a different strategy.</p>

If you're new to DDD and not sure where to start, this process will guide you step-by-step - ddd-crew/ddd-starter-modelling-process

If you're new to DDD and not sure where to start, this process will guide you step-by-step - ddd-crew/ddd-starter-modelling-process

This post is a continuation of Small and simple business applications using SQL.

This post is a continuation of Unclean architecture.

Clean Architecture is a way of structuring a solution such that dependencies and infrastructure concerns are kept separate from business logic and the domain model. It's frequently used with Domain-Driven Design and can easily be built with ASP.NET Core using a solution template described in this article.