Tagged "oop"

Back to Monoliths

So Amazon Prime Video (of all people!) published a blog post about how they’re returning to monoliths, relayed by DHH, generating lots of noise, to the point that even Dr. Werner Vogels himself, CTO at Amazon, had to pour some thoughts about the subject.

Microservices or Not? Your Team Has Already Decided

Let’s take a somewhat tangential approach to the subject of the Microservices architecture. Most discussions about it are centered around technological aspects; which language to choose, how to create the most RESTful services, which service mesh is the most performant, etc.

Removing Singletons

Problem: your code has a big badass manager class with a singleton interface, and you would like to have more flexible, testable code.

A Watch - from an OOP Perspective

A watch might be one of the most common types of objects, but it remains also one of the earliest pieces of human craftmanship to show an extreme level of complexity, all contained in a small amount of space.

AOP and the DataServices Project

Five years ago I worked as a Software Engineer for a startup, based in Geneva, Switzerland, which had the goal of creating a web-based systems management console, to control and monitor the status of large computer installations, much like Microsoft SMS (Systems Management Server) does.

Preferred Programming Languages

There are basically 5 languages that I really like. For several reasons.

What Will the Software Architecture Discipline Look Like in 10 Years' Time

This is a tricky question; after all, Bill Gates himself published a book in 1995, “The Road Ahead”, where he only slightly talks about the World Wide Web:

Inversion of Control, Ruby and Rails

Next week I will be in Belgium working with the Thales team in Brussels, building a new software solution (for a customer of the public sector that I cannot disclose here) using the following technologies:

About code and eggs - excuse me?

The purpose of this article is to show that the current trends in software development owe a lot to ancient mindsets, and that some good old Object-Oriented Programming (OOP) programming constructs are no longer accepted in modern business development scenarios.