We can recall that the only real boss of the architect is requirements . The architect may not listen to us, to developers, to customers, to anyone. But the requirements are the indisputable boss. So, there is not mystery neither magic over the decision making process, it must be ruled by the requirements. But, what was this project about? In fact, it was about consuming a SOAP service provided by a third part, to allow our internal business side to update the customer case-file or unique digital profile. As part of this project, the number of request from our platform to the provider side must be under certain control or below a number we can consider acceptable for our consuming rate. Also, for both services, our own service and the one from the provider, working with bio-metric data is a must, it involves fingerprints and face recognition. So let’s start looking deeper into this project.
Suele pasar en este mundo de la tecnología que, cada cierto tiempo, tenemos a todo el mundo hablando y usando determinada solución, producto o herramienta, sin ninguna otra razón de peso mas que la moda, o que el "main stream" de turno dice que es la forma correcta de hacer las cosas. Entre esas tecnologías o soluciones de moda nos encontramos con los ya harto renombrados, microservicios . Todo el mundo habla de ellos, todo el mundo migra hacia ellos, ... pero, y siempre hay un pero, ¿son en verdad tan beneficiosos los microservicios ? ¿Cuanto hay de mito y cuanto de, ¿fea?, realidad?