Once we used to say API - REST API etc, later a more generalized and wide term arrived => microservice!
But don't ever assume API and MS are same..!
Both leveraging the "resource capability" exclusively.
API is the communication mechanism for a microservice. The other one is defined as a single purpose simple service that can communicate to other services. means, it can be a UI to a extensive functional component (hardware/software).
NB: The tech notes are all my personal views from experience.
When finding a solution to a real world problem, if it involves a software component, definitely starts a "pain" to the developers. The environment configuration, as is to the tech solution, then the logic, optimization, unit testing, integration, business verification, deployment in stage and prod, after all the actual scenarios where mostly all the stake holders missed something. But at the end, the whole blame comes to the one who "codes" it. Yes, the pain of being a software engineer is not so easy especially in development. Apart from mental stress, on calls, after all the physique posture problems, long lasting health issue... But still its a passion :)
Comments
Post a Comment