A bit of background: I work in a small finance company in Tokyo with ~20 people in IT. The structure of this department is everyone responds straight to the CTO so it's somewhat chaotic.
I am the front-end person in a team doing a single product. Besides me, there's only the back-end guy (our direct boss is the CTO). As per our CTO instructions, the back-end is structured with microservices in go. So 1 developer is designing, launching and maintaining something like 8-10 microservices. Things also change quite frequently from our CTO random recommendations.
I feel this is madness, and our main back-end guy works very long hours and is visibly burned. I am worried both for him and for the quality (or even launch) of the product. There's no single process or workflow that works smoothly.
How common/rare is this about microservices? What would you recommend me doing (besides jumping ship)?
I am the front-end person in a team doing a single product. Besides me, there's only the back-end guy (our direct boss is the CTO). As per our CTO instructions, the back-end is structured with microservices in go. So 1 developer is designing, launching and maintaining something like 8-10 microservices. Things also change quite frequently from our CTO random recommendations.
I feel this is madness, and our main back-end guy works very long hours and is visibly burned. I am worried both for him and for the quality (or even launch) of the product. There's no single process or workflow that works smoothly.
How common/rare is this about microservices? What would you recommend me doing (besides jumping ship)?