Microservices

I have previously approached microservices during our Web development course, although we had a lot of issues with that course such as the pacing being too slow due to some students from other career getting stuck several times. And we also had issues with us not knowing the basics of web development and then teaching us microservices telling us about how they solve a lot of issues, but us having no idea what those issues were.

Curiously, we were taught about microservices using Amazon console, business that the article mentioned several times. Now knowing a bit more about web and after reading the article that finally explained some of the problems they solve, I begin to appreciate them more and would like to learn to better use them although with a better pacing. It sounds indeed a lot better to only have to change a service instead of changing the whole code and then having to rebuild and using them it was really comfortable to use python to manage the database and only having to call the service in the JavaScript, because as long as I respected the interface, I could make any change in the Python and could leave the rest of the code alone.

Also, something we never saw in class was that part of designing for failure on how to handle the possibility that one of the services was unavailable although I believe the professor did not deemed it necessary as all of our microservices were lambdas in AWS and it tends to be a robust service. Although I feel like this may have been an important detail to learn about. Probably the teacher was right in teaching microservices although I feel it would have been better as a topic or a second part of the course instead as the basics.

Comentarios

Publicar un comentario

Entradas populares de este blog

Is design dead?

  “Any unneeded complexity makes a system harder to change in all directions except the one you anticipate with the complex flexibility you put in”. I believe that quote of the reading is the one that does a better job explaining why you need simplicity in the code and the strong point of programming for the present, not for the future. As indeed making a part of my code easy to modify would need that I make the assumption of what type of change would be needed in the future. I really like his moderate posture or coward as he calls it because in some of the things he mentions regarding design or having absolutely no architecture at all, do sound too extreme especially when in situations where is clear from day one that you do need a database. I particularly like his posture in regards to architecture of doing it, but take it as a sketch not something written in stone as you do not know what possible requirement changes come in a project or what specific issues come during the programmi
Leer más

SOLID

  The SOLID principles are really good advice and were explained in a really simple way during this article. Some of them I had already heard as in the past I have read one of Uncle Bob’s books during the Videogame project course. The Single Responsibility Principle is the only one of the principles that until now I always have in mind while writing classes, although being honest just as the article says it is not always that straightforward what would be considered doing only one thing, so sometimes I may not apply it perfectly. The Open/Closed Principle and the Liskov Substitution Principle those are principles that are new to me and certainly go against some of the things I knew.   Because I had learned to use inheritance in those situations, although reading the article I agree that abusing inheritance may not always be a good idea as it may leave the code in an unpleasant state or generate side effects. The Interface Segregation Principle I never had thought about doing that,
Leer más

Software Craftsmanship

  I have been trying to avoid of thinking of programming as a craftmanship since some years ago because we were kind of thought that it was incorrect. During our software development courses we were taught that treating it as a craftmanship was what caused it. But the way uncle Bob explained it as a craftmanship did resonate with me as indeed you do feel proud of your code when it works, and when you manage to program an elegant solution or a clean code it does feel better. Also, everyone has their own way of programming for example when in a group project I see a variable with an unholy name such as ‘iiiiiiiiiii’ I immediately ask Óscar if he did it, and with people you have programmed multiple times you get a feeling of how they code. Maybe it is not a wrong way to see code after all if you can follow the software craftmanship manifesto, which indeed as they say it is not nearly as popular as the agile manifesto. The points in them do sound like really good programming practices to
Leer más