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

BrainExpanded – Web app and Data Sources

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

3 days ago

BrainExpanded – End-to-end working

Imagine a world where your memory is enhanced by a team of intelligent agents, working…

3 weeks ago

BrainExpanded – Login State Caching Issue in iOS Share Extension

As part of the BrainExpanded project, Iโ€™m building an iOS app that lets users easily…

2 months ago

Is AI Good or Bad?

Artificial Intelligence (AI) has rapidly evolved over the past few decades, becoming an integral part…

2 months ago

BrainExpanded – Copilot

Happy New Year everyone! I was planning for my next BrainExpanded post to be a…

4 months ago

BrainExpanded – The Timeline

See "BrainExpanded - Introduction" for context on this post. Notes and links Over the years,…

4 months ago