Hacker News new | ask | show | jobs
by aespinoza 4173 days ago
He might be trying to learn more about Microservices by identifying the structure in a current project. So it is a valid question.

Those names are useful to communicate ideas. It is just like software patterns. It doesn't correlate to a direct implementation of the pattern, but a pattern correlates to an idea, and it is extremely useful to communicate them. Microservices are just that.

1 comments

That's a bit like saying, i'm trying to learn about supercars by asking if this car is a supercar. It's a generic classification. Moreover, knowing how to classify it does not change how you design it or why.

Unix programs are non-networked microservices. An LCD controller and display driver could be described as a single-function single-process non-networked microservice. It really does not matter what you call it or how it is categorized; it just is.

Better communication is great, but we don't need a new word for every idea. Especially if people get wrapped up in what counts as that word.

Microservices is a new "word" assigned to an old idea. But it is still new for someone. I agree with you, I just think this is a valid question. It might be improved by asking "Why is this is/isn't a Microservices architecture?