HOW to ARCHITECT for DEVELOPERS
The majority of new Technologies are refined and renamed old ones
Fault tolerance requirement was known for a long time before Microservices were defined. This requirement has surfaced again because when working with relatively small applications or components like Microservices, it is much easier to observe fault tolerance and it replicates at a higher scale than when working with monolith applications. There are no any special …
Continue reading “#Sib #Pattern for #Microservice #Fault #Tolerance”
For people who are in the IT industry for years, the comparison of SOA to EDA and vice versa is not news. For the new generation, their fundamental difference may be not that obvious, especially, when the architecture implementation relates to Microservices. The basis of SOA is a client-server/service model. Yes, it is the old …
Continue reading “How TO: #Microservices and #Eventholder – what is what for”
For the last 2.5 decades IT architects used Unified Modelling Language (UML) notation. This graphical notation and the concept supporting it was created by Grady Booch, Ivar Jacobson, and James Rumbaugh while working at Rational software. In 1997, the Object Management Group (TOG) adopted UML as a standard for its members,. Later on, UML became a …
Continue reading “⌗ARCHIMATE TRANSFORMES ITSELF INTO LOREM IPSUM”
Not long time ago, hashtag#McKinsey & Company decided to advise Enterprise Architects on how they have to change themselves to survive in the digital revolution. Well, it might be a noble mission if such a “business case” was strong. McKensey – the trusted advisor to the world’s leading businesses, governments, and institutions – had identified …
Continue reading “DOES #ENTERPRISE #ARCHITECTURE NEED #PROTECTION IN A #DIGITAL WORLD?”
HOW to ARCHITECT for DEVELOPERS 