Whether in life or Cloud system design, you should always act to decrease, not increase maintenance cost. Keeping the number of moving parts down helps with that goal.
Microservices represent a great solution for a Cloud problem. They are not a solution for EVERY problem. Do not try to use them as a selling point for on-premises software.
California clipper, Wikimedia Commons The California Gold Rush (1848–1855) lasted only 7 years. In that amount of time, it brought 300,000 people to California, invigorated the US economy, played a key role in ushering California to statehood in 1850, and caused a precipitous population decline of Native Californians. One of the most profound lessons of... Continue Reading →
Like planets, your micro front-ends never stand still - don't hobble them with irresponsible component reuse.
This post is not here to bring you anything new as it is for me to run a victory lap. If there is anything I blogged about with any consistency, it was about microservices. There are many articles in this blog addressing various problems you may face when attempting a microservice system of a non-trivial... Continue Reading →
Picking the 'right' Web component model is only the beginning. Fitting the component into the page visually, figuring out what is happening in it events-wise, and feeding it data from the server is the real battle.
In one of my favorite movies "The Blues Brothers", the wife of the trucker pit stop owner proudly exclaims that they play 'both kinds of music - Country and Western'. Readers of my blog know I too tend to serve two kinds of articles. In think-pieces, I tend to pontificate on a topic that buzzes... Continue Reading →
Practice architecture in motion - infuse it into code while it is being built, don't make it a separate phase.