How to repair a rocket without launching it or how TDD helped me, small review.

One upon a time I worked with a micro-service architecture. I had been working with different architectures before. They were logical and workable. But the current project was little bit strange.
We did almost everything according to micro-services architecture. I began reading about micro-services. My opinion is still exited. I like them. I started meeting articles about bad approaches and problems. I realized the real problem was that the micro-services architecture likes a crown for a king. In our case it was a crown without king. I do not want to urge the project. Because I was a simple implementer. I could not image if somebody had been in such situation. It that was my case and my problem. I had a task and a repository. The project was not deploy-able. I could not set up the whole network of services. Yes, there were some lucky things these helped me. Before I had good practice of TDD. There were some domains of logic. I found a problem, fixed it. I made the project testable, made a test. The test recovered the domain data, afterward I tested changes applied. The test revealed few situations that it showed that it worked and it approved the a level of quality. What is about deployment? I do not know :) Now this is the problem of a DevOps. I hope he has done it. My staff have done that I can report about. I am a developer. Nowadays I do tests regularly. I can not only call benefits of them. I feel the benefits of them. Believe me!