Problem Statement When upgrading from a monolithic architecture to a microservice-based architecture, the designer(s) can encounter situations where one service depends upon another. Upgrading the dependency can potentially disrupt the service, and in an extreme situation, the entire system, and possibly affect the development of the system. The solution to this problem is the Proxy
Click edit button to change this text. Marcel discusses Agile transformation and delivery including impact on development and setting up a skilled team. With special attention to agile at scale and other enterprise opportunities.
Developing a DevOps strategy? Here is how you get it done with CITA-Professional Kumaran Anandan.
This blog post is one in a series that will give you some insight into the full day training class (Microservices Solution Architectures) I will be teaching at the ITARC Austin on October 6th, 2016. That's a great question. Maybe you shouldn't. I have had this debate with more than one person: "Isn't a microservices architecture just
To implement an architecture that takes advantage of container technology, one way to persist the data has been to use a separate data container. In my case, I am using Jenkins in a container, and I want to save the configuration/jobs/history from my CI flow. Ideally, this container would a part of some kind of
The signature benefit of a microservice architecture is that its highly granular nature allows for a great deal of flexibility in composing applications. Components are simplified by virtue of a high degree of focus. The ability to replace individual components is enhanced by the modularity inherent in the style. A very significant drawback to microservice
Software architecture defines the different parts of a software system and how they relate to each other. Keeping a code base matching its architectural blueprint is crucial for keeping a complex piece of software maintainable over its lifetime. Sure, the architecture will evolve over time, but it is always better to have an architecture and
By Mark Sigda I have to admit, as an architect with a long history in distributed systems, that I still love the concept of SOA. I’ve also tried to make it happen (more than once) and failed miserably. As a former developer, something always troubled me about SOA. I didn’t see it at the
By Alexander von Zitzewitz The metaphor of technical debt is gaining more and more traction. Originally Ward Cunningham used the term for the first time in 1992, describing it like this: “Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a
