Diego Pacheco Tech blog

Too many information, is not even a joke. We live into a high information overload. But how much is useful? Sometimes i think is just noise, most of times more noise them anything but there is good stuff in the middle so it requires us to filter. I link to have a directions otherwise you might got lost into the middle of the news feed, twitter and flood of infoq, youtube and vimeo videos. In the past i got my left reading a lot but most of not that interesting or useful to me, luckily today we have better tools like twitter and prismatic but we still have to deal with the overload and flood. Sounds like i`m saying you need have a big data stack for you to figure out what todo but is not. So for me starts with the passion, so whats are your fields of interest or what are the things you want get better, i try to not focus in so many things at the same time but 4 areas most of time.

Complexity is the center of the universe today. Many things are important to have success and archive great results in life and work. Endurance is a attitude that is missing. Actually when i look people that got great results - all these people had endurance. Good things dont come easy, people talk a lot a about several attitudes now a days like entrepreneurship or creativity but they are focusing on the wrong sides of the attitudes. Nothing great comes fast - So what is the point of sprints? We need test ideas quickly and throw they away right? thats our lean startup FAST FOOD mindset right? I`m saying that wrong but IF you belive in something, in a vision, in a direction you will need endurance.

One of the real game changing benefits of SOA / MSA(Microservices Architecture) is flexibility. Flexibility give you power todo things as you wish, in order to have flexibility you need have decoupled things but hold on a second, in a service oriented world everything is done via a contract and services are coupled to this contracts. How could you still have flexibility if the contract changes you need rebuild all consumers and deal with the changes? Even worst than that - whats makes SOA different from webservices or procedures calls on the data base? (remember soa/msa is not about technology is about principles and design/arch.)

Working as a consultant many times i raise the bar of the role architecture in great software. As solution engineers we often talk about software architecture. When we are working with SOA / MSA (Microservices architecture) we need realize that there is more than one architecture. You could and most likely will have a middleware or container or bus or platform you do your business work but each *thing* needs to have its own architecture. For SOA/MSA the citizen of first class are Services, so basically you work with Services and you just "see" services, in the end of the day what matters is raise the level of abstraction and leverage from that in business perspective.