I would add that each service being able to provide it's own client via a simple feign client declaration for any other services to have a dependency abstracts the "RESTY" Stuff and isolates it to limit duplication of code and help with SPOC.
We moved in the build in Aug. '14. The drywall ceiling had one small piece hair crack. We ignore it, but after one year, have 5 area have this problem. Also, outside desk, missing over 12 inches exterior flushing. We reported those problems to the developer. Their answer is "they are not developer's responsibility for those hair cracks. Not worries outtside exterior-flashing, they will not have any effect in your inside living conditions". We are disappointed.
the thing from my view point (junior siftware engineer) is, when this kind of problems started showing up, how did it end up getting such a complicated situation where you have an enormous number of different frameworks and blablabla I mean at the end of the day you are just requesting/delivering damn data from server
Think of the situation when you have hundreds of servers, each of which has its own subset of services and each of which should be able to consume others. How would you manage this bunch of machines and services? How would you use them effectively? How would you prevent the situation when one server is overloaded and 99 are not doing anything? Moreover, suppose one of these servers crashed, how would the rest of the servers know that this one has failed? How make them stop using this crashed server and get exceptions? And when this server gets up, how would the rest of servers know that it has waked up? That's when these "blablabla frameworks" come to rescue you from this pain.
I would add that each service being able to provide it's own client via a simple feign client declaration for any other services to have a dependency abstracts the "RESTY" Stuff and isolates it to limit duplication of code and help with SPOC.
Fantastic piece of work!
We moved in the build in Aug. '14. The drywall ceiling had one small piece hair crack. We ignore it, but after one year, have 5 area have this problem. Also, outside desk, missing over 12 inches exterior flushing. We reported those problems to the developer. Their answer is "they are not developer's responsibility for those hair cracks. Not worries outtside exterior-flashing, they will not have any effect in your inside living conditions". We are disappointed.
the thing from my view point (junior siftware engineer) is, when this kind of problems started showing up, how did it end up getting such a complicated situation where you have an enormous number of different frameworks and blablabla I mean at the end of the day you are just requesting/delivering damn data from server
Think of the situation when you have hundreds of servers, each of which has its own subset of services and each of which should be able to consume others.
How would you manage this bunch of machines and services? How would you use them effectively? How would you prevent the situation when one server is overloaded and 99 are not doing anything? Moreover, suppose one of these servers crashed, how would the rest of the servers know that this one has failed?
How make them stop using this crashed server and get exceptions? And when this server gets up, how would the rest of servers know that it has waked up?
That's when these "blablabla frameworks" come to rescue you from this pain.
Is there a slide available for this video? The given slide link is deleted