Architect Consultant blog

Key Takeaways             Three primary aspects of evolutionary architecture: fitness functions, incremental change and appropriate coupling Design for change on multiple dimensions (technical, data, security and operational) Combine DevOps (Continuous Delivery) practices with fitness functions to verify the architecture       Migrate to another architecture for good reasons (for example better team structure and operational isolation), not because “it’s the current trend” Building Evolutionary Architectures is a promising title for a book. I was also triggered and wanted to read the book. This is a review of the book with my own humble opinion. First a short description of the chapters is given. Chapter 1 - Software Architecture A definition of evolutionary architecture is described, which states that it supports guided, incremental...

Introduction Testability is one of the underestimated qualities of software. This is also the case for WSO2 ESB projects. However it is important to design the integrations for testability and this starts with the way you setup the proxies. This blog gives some guidelines which you can use to design for testability. Sequences Sequences are a way in WSO2 to group Mediators. A proxy has by default an in-Sequence, out-sequence and optionally an error-sequence. These sequences can be split up in sub-sequences and this is a good way for reuse, but also a way to split up the design. A proxy usually contains the following functional parts: Validation Transformation Sending to an endpoint   These parts can be put in separate sequences. This has the advantage that the part scan be reused in other proxies. This is also the way to enable testing for these parts.  Design for testability The sequences are the basis for the testability of WSO2 ESB pr...

Introduction Unfortunately i did not went to the WSO2 Conference in Asia  but i went through the presentations and this blog item describes some interesting topics i came accross. There were a lot of different tracks: API Management  Cloud Strategy Integration' Security Governance Architecture Analytics DevOps Internet of Things (IoT) API API (Management) is a hot topic. Almost all reference architectures use APIs to expose functionality, either to mobile apps or other apps. It is used within Microservices as contracts, it is used in connected enterprises that want to expose their APIs into the API economy system and it is used internally to manage and govern services. IoT Internet of Things is a also a big thing, so also at the WSO2 conference. The WSO2 IoT Server was announced in 2016 Q2. Features of this product: Implementation of WSO2 IoT Reference Architecture Device Management Device Analytics Device adapters ...

Introduction I wanted to know more about DevOps because I agree with the fact that we need to coorporate more and remove the barriers between departments. In the end I was a little disappointed by this book. It gives some high level tools and techniques but it could be much more ... In my opinion a change would be that someone from Operations will really participate within the project team and looks at it from an operation point of view. This way also these requirements will be taken into account and the system will be more easy to operate. However there were also some interesting chapters so lets review. Chapters The book contains 7 chapters: Evolution of a Software House No pain, No gain Plan of Attack Tools and Technical Approaches Culture and Behaviors Hurdles to Look Out For Measuring Success and Remaining Successful Chapter 1 - Evolution of a Software House As the name already suggests, this chapter is about the evolution of a software house. First it ...