Some architectural choices

One of the first is, of course, the database. By the way, I should even say the persistence mechanism because a database is a very well-known persistence mechanism, but there are others, as we will see at the end of this section. Some other technical considerations will have to be dealt with – in particular, on the streams of data.

This section will also be an opportunity for a little rant about the dogmas in IT, and how they delay the long-awaited industrialization of information systems. Lots of technical choices remain based on the knowledge of the teams available rather than on the adequateness of the functional problem at hand. This is not to say that competencies should not be taken into account, but training should sometimes be forced on technical people who have not changed their way of thinking for decades and may hinder your information system development because they simply apply the wrong tool to the problem. You have likely heard the...