Bricks

Micro services is a trend that is becoming really popular on the industry, several companies that their products were built with the monolith idea are starting to create projects that will migrate the big bad monolith into different micro services. Now there are a lot of several frameworks that are given support to micro services. From both parts from the front-end and the back-end. Takes to this advancements we are also experimenting a whole new way of creating software. The idea of server-less API is becoming more and more relevant.Front-end frameworks now are focusing on creating a complete bundle of files that the user can see in its browser and be able to talk to the different Micro services that the front-end application gives access to.  We can see on how the different technologies are moving towards this type of architecture. Now it doesn't mean that this type of architecture is the perfect solution for all the business problems. It actually can create several problems that sometimes people tend to forget and just keep creating more and more micro*services. The first one is creating to many micro-services and making sure the whole application depends on those micro services. This is something that can create big debate, and that is when is a micro-service big enough? Or which should be the coverage of Micro service? Sometimes companies can create to many services and when this services communicate with each other, this can create a problem on maintaining the different services we have created. So we can see that good design in something that is so modular is still relevant. In my personal option I really like the idea of Micro-service, especially from the part of configuration. The Monolith approach usually would require an extensive knowledge on how to configure the server and how it will respond for the different requests. Which hierarchy of assets should the project have so we can shows those assets to the user etc.Now with micro-service we only focus in the part of making sure we can create a server that can receive http requests , and just separate each method with their respective paths and method types. This makes the development more focus on the part of business which it will increase productivity.

Comments

Post a Comment

Popular posts from this blog

Mutation

Meta programming helps us in creating languages or programs that could facilitate the day to day tasks. The biggest example of this case would be any low level programming language we use. Assembler is a language that requires a lot of time and knowledge so we are able to program a simple task. So of course trying to teach a lot of people Assembler , can create a lot of problems in so many areas. People not understanding the material, programs with a lot of bugs that are hard to track and of course big amounts of code to solve simple tasks causing the level of complexity to maintain that code to increase. Therefore low level programming languages were started to be created so programmers could have a better understanding on how different programs would work. Yet higher level programing languages started to emerge , cause of the facility of learning this type of languages. The biggest examples are the SQL languages , even if people don't considered it as a programming language, is a
Read more

Repairs

Software Development is one of that areas that the people who are involve it will see so many aspects of it that is hard to describe to a newcomer what are the things they need to focus on. This is because the induistry has changed in a drastic way through the years and it will continue to change with time to time. Now a thing that people should understand in the industry is that everything is related to the base product which it is the code. With new type of frameworks and the way we handle the process to deliver requirements, the first that thing that matters the most is that it should work not matter the cost. Now I am not saying that delivering a perfectly documented code that doesn't work is a better solution, we should always deliver a working product to clients. Yet we have to considered the type of code we are delivering to them. Think about how easy is to maintain or understandable it is for other future developers. Cause even if this things doesn't impact us they will
Read more

Pillars & Arcs

Creating a complete program can be something so simple or complicated depending on the reach that the program needs to satisfy. This is an important idea and for us as Software Engineers something we don't need to forget. Usually as how as startups are growing in numbers and in size most of them roll with the same idea. This is that the program should only be able to solve the problems or requirements that were presented. The minimal working product that we can show to clients is the best option for developing new products. Even in the practices for managing the new startup projects are more guided to some type of Agile methodology. This is because it helps to adapt to the ideology that i mentioned before. Developing fast and minimal to the current requirements that the client needs. That is in essence the motto that a lot of companies are guided with. We can see it deviates from the old ideas of cascade methodologies , where usually it was a whole process on determining which woul
Read more