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.
The journey of a software engineer is a complex and often underappreciated saga. They start as programmers, mastering the intricacies of code, but their role quickly expands far beyond just writing lines of logic. In reality, a dedicated developer ends up wearing many hats—business analyst, architect, troubleshooter, deployment expert, and sometimes even a therapist for systems and people alike. Despite their best efforts, developers often find themselves at the receiving end of blame when things go wrong. End users might complain about a feature not working as expected, the business team might point out gaps between requirements and reality, security might flag issues that slipped through the cracks, and operations might raise alarms over performance bottlenecks. Yet, when it comes time to find a solution, all eyes turn to the developer. In the software lifecycle, any bug, oversight, or delay typically falls on the developer's shoulders. Even when the root cause lies in infrastru...
Comments
Post a Comment