This video takes a serious but light-hearted look at the role of enterprise architects in modern IT organizations. Software architects in the enterprise are often regarded as ivory tower residents who bestow their utopian plans upon project teams in the form of colorful diagrams that bear little to no resemblance …
Nowadays everyone in software architecture is talking about microservices and how cool they are. That is true, but not all business needs to move to microservices, you can still use a monolith software architecture and make it more fashion by applying some of the design/elements that you have learned from …
Moving from a layered software architecture to a vertical slice architecture can be a bit daunting. We remove abstractions, complex structures, and focus building on the axis of change, then what’s next? What new structures, patterns, and policies will need to be introduced in this style of architecture? How will …
Although software architecture is a key factor in determining the success or failure of a software system, software professionals throughout the industry continue to struggle with questions like: What exactly is a software architecture? Why is software architecture important?
MetaCase has launched MetaEdit+ 5.5 to make access and governance of collaboratively created software development models easier. The new MetaEdit+ release extends supports for collaborative development with model access rights per user and project.
Every complex software product has a variety of software architecture concepts that directly affect the code base. Which types of components do we have, how do we identify these components, how do we structure them and how are they allowed to depend on each other and through which interfaces. However, …
Today it seems like Microservices are the de facto standard for a system architecture, but do they really live up to the hype? The talk will show you an alternative approach – how we can tame complexity with the help of a clean, monolithic software architecture that is modular to …
We often think of software architecture as one of those things we just have to do right at the beginning of a project, often using fancy tools. This talk offers an alternative. What decisions would we make differently if we had the ability to rapidly evolve our architecture?
