Some clarity on what the buzz around micro services is ?

Question

Hi guys ,I keep hearing a lot of buzz around micro services and a lot of high paying roles for back end distributed engineers.I have some idea about it but I never really worked with any team that uses distributed engineers&nbsp;Below are the questions that i am looking to get cleared about back end distributed systems engineer and its relation to a full stack engineer&nbsp;1) i know what a distributed system is ... in short .. a system that is trying to achieve fault tolerance , scalability &nbsp;with a very low latency prioritizing based on the needs kd the problem at hand .... But what does a software engineer that is placed in such a team do explicitly on his day to day&nbsp;&nbsp; &nbsp; &nbsp;a) does he write APIs and SLAs (OR)&nbsp; &nbsp; &nbsp;b) does he design the back end dsitribution like writing scripts to distribute the data, know the pulse of servers, write scripts to manage master-slave architecture etc etc &nbsp; (OR)&nbsp;&nbsp; &nbsp; &nbsp; c) is he a network engineer that understands the concepts of networking and use them to reduce latency and stuff. (OR)&nbsp; &nbsp; &nbsp; d) something other or combination of some other skills , please provide me with an elaborate answer, that clearly demonstrates a &nbsp;distributed engineer role.&nbsp;PS : please do not provide a standard template answer or some answer that describes an ideal distributed engineeer that only exists in job postings or at principle/ distinguised level engineers. Please provide answers in such a detialed way that can be same as helping a mid level or entry level distributed systems engineer to on-board onto your team.I understand the standard interview process of system design.. i just want to know what a mid level distributed engineer &nbsp;does on his day to day and why is he paid significantly more than a full stack engineerMade a lot of mistakes hearing to buzz , getting into that role only to realize it is not something i expected. Dont want to make such a mistake againI thank you and appreciate your time in advance&nbsp;

19f9wri6faob8aw · Accepted Answer

This post is way too long, but I'll attempt to answer. As a distributed engineer, you're mainly evaluated on system stability. Especially for an organization with many micro-services, you'd build network layer tools to ensure that they are operating efficiently amongst each other and are coherent. A big thing with micro-services is fault tolerance, where you want to be resilient to other services going down and providing ways to go around failures.

holupmane · Answer

I doubt this answer is detailed for what you’re asking but mostly A and B IMOA: Write API’s to automate backend processes, and optimize its performance by implementing worker queue clusters, etcB: Siphon streaming data into their respective databases which are optimized for a business/app based case, while monitoring all the sever + cluster health kpis

Some clarity on what the buzz around micro services is ?

About

Software Engineer

Members