Techwaves

When the application developed some years back, when aws was not in picture (atleast in our circle), the communication mostly with http for the easy implementation. On a later stage, we too adopt the evolved update of communication as aws SQS into the system. The system was working perfectly with less transactions. But when it scales, it started to get "complaints" as many transaction updates failed. Investigating the real issue took sometime as all are in an opinion that the "code" would have missed any logic.  The real "issue" was the SQS url dynamic IP! Then system has to implement with VPCE, with proper re-coding to modify the sqs sending method. NB: TechTides involve a kind of experience from the tech journey Bonus: https://www.slideshare.net/arenishr/tipsgooglepptx https://www.slideshare.net/arenishr

From a background of chemical engineering, switching to Software engineering was a big deal at that time. Even the skills, reasoning, adaptability, learn to know everything made it flow seamless. But in this period, the vast and wide spectrum created a hallucination.  For a software engineer, what matters actually is the "logical analysis to find a solution to a problem that the end users or humans face". From that perspective, if we drive our passion, learning is much easier. Now the hurdle of time and resources come. Time matters if we need to succeed in the industry. Resources - it is again a wide spectrum from tools, technologies to articles or blogs. GIS : Abstract: the GPS plays a vital role in all industries as well even in day to day life. People are much social but virtual only. Say for an example, they are socially talking, chatting or reading with their friends in another country and enters into a public meeting area the unconsciousness creates disturbance and n

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.