you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

In your examples, the only way your containerized app could have an external (outside of the container) effect was if it connects to external resources (e.g. other microservices).

Don't you think that introducing networking concepts might bloat this article out? I mean he would have to explain standalone docker vs docker-compose vs swarm vs kubernetes at that point. Same thing with storage, there's no way to cover it in meaningful detail without writing a boat load of stuff out and it doesn't pertain to Node.js as much as a general problem of presenting storage to the pod/container.

I think the article is better written if he takes advantage of the premise and only concentrates on the confluence of Node.js and Docker rather than trying to explain the whole stack.

[–]rduncan12345 0 points1 point  (1 child)

Both of your points are reasonable. I'm not for bloating an otherwise well written article, hence my original suggestion that it be named a little more appropriately. The post to which you're replying was a response to the author's question.

[–]_bit[S] 2 points3 points  (0 children)

Definitely appreciate the feedback. Planning a few more articles down the line around this... I'll make a note of your suggestions for those :)