Moving behaviour from the endpoint to protocols

In case you do not follow the comments on my blog posts, here’s another great one about moving the behaviour from the endpoint by Michi and my response (almost agreeing! 🙂

Of course I am not suggesting that we completely move to a world where all applications are built using the principles of service-orientation; only where it makes sense. There is always going to be a place for object-oriented design and applications.

Behaviour and semantics can be decoupled from endpoints and, instead, captured by additional metadata (e.g. workflow, semantic languages, etc.) where it makes sense.

And of course, nothing is new. We are just trying to clearly identify the differences between S-O and O-O and document the potential advantages/disadvantages.

Recent Posts

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

3 weeks ago

Enhancements in Graph Model: Dynamic Entities & Full-Text Search

As I continued work on BrainExpanded and its MCP service, I came to realize that…

4 months ago

GraphModel: A .NET Abstraction for Graphs

Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…

5 months ago

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

6 months ago

A Graph Model DSL

Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…

6 months ago

BrainExpanded – Web app and Data Sources

As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…

7 months ago