Category: Client /server

Application Migration, Client /server, Domain driven design, Enterprise architecture, Frameworks, Hibernate / nHibernate, Java, microservices, Service oriented architecture, Software architecture, Unit testing, Value objects

Microservices. The good, the bad and the ugly

Back in 1988, when I was first employed by a company for writing software, the world was fairly simple. The development environment we had was character-based, the database was integrated and traversed with cursors, and we built a whole new administrative system covering everything but the kitchen sink. It took us five years to complete the project, basically because the […]

Agile, Client /server, Estimation, Smart estimation, Smart use case points (SUCP), Smart use cases, Software estimation

How to kill your estimates

It must have been about twenty five years ago. I was working for a large international consultancy firm. One of the reliable ones. The ones that you would think that had everything worked out. But I guess this was merely the product of my imagination. At one time two colleagues and I were working on an estimate for a bid […]

.Net, .NET RIA Services, ASP.NET, ASP.NET MVC, C#, Client /server, Domain driven design, Entity Framework, Extension methods, Frameworks, Hibernate / nHibernate, Model driven development, Modeling, Service oriented architecture, Silverlight, Smart use cases, Smells of bad code, UML

A book on pragmatic software architecture, patterns and frameworks?

One of the major items on my wish list – that is on the professional half of it – is to write a book that displays my ideas on software architecture, patterns and frameworks. Yes I know, there are many books on software architecture, and there are many books that explain patterns, and yes there also are a lot of […]

.Net, Anti-patterns, C#, Client /server, Design patterns, Domain driven design, Frameworks, Microsoft CRM, Service oriented architecture, SharePoint, Software architecture, web part

Client/service architecture. Domain driven development in the distributed era. Episode IV

Go to episode three. Go to episode two. Go to episode one. In case you’re wondering why doesn’t this dude come to his point, you’ve probably missed it. I’ve made it already. The point is: you should always have a single point of truth, and at most have it reproduced on the server side. Which in most cases you don’t […]

.Net, Anti-patterns, C#, Client /server, Design patterns, Frameworks, Java, Service oriented architecture, Software architecture

Single point of truth. Domain driven development in the distributed era. Episode III

Go to episode two Go to episode one Client / server could have been a much more successful era in software development, if it wasn’t for this copy-and-paste programming, leading to applications that slowly became unmanageable. I have seen this anti-pattern occur in any of the popular client / server technologies. Without exception, whether it was Visual Basic, PowerBuilder or […]

.Net, Anti-patterns, C#, Client /server, Design patterns, Domain driven design, Frameworks, Java, Service oriented architecture, Smells of bad code, Software architecture

The merits of two-tier architecture. Domain driven development in the distributed era. Episode II

Go to episode one. So now you’re stuck with this two-tier architecture. Is this a problem. Well, not yet. However, it can become a huge problem, and it has become a huge problem in many, many client / server applications, in a vide variety of technologies, including several types of (legacy) web application technologies. The truth is out there The […]