|
|
|
|
|
by svatwork
1849 days ago
|
|
I don't see anyone mentioning a definition of microservices... How can you talk about it if you don't define it? I've split up an application for a project into separate containers with docker-compose. They shared some environment state with a dotfile. I don't have to reinvent the wheel and can just pull some services into it and tag them so I can easily rollback and roll forward. I can offload storage with Docker's storage driver. The services talk through sockets, so it's easy to verify the uptime. The services are implemented in different languages, because I don't believe that there exists one golden language that can solve all problems. Is that microservices? I don't know, but it works really great and it doesn't feel like there's any overhead. Another example. I work in a team where two services use JSON schema validation, and they can't be reconciled. Agreement between schemas takes so much overhead, because there are different expectations, leading to 90% of the time discussing schema changes in pull requests. |
|