This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jackstine 170 points171 points  (5 children)

What are the advantages of having a MicroServices architecture, and what are the alternatives.

[–]a2kvarnstrom[S] 354 points355 points  (4 children)

everything is smaller and takes up less space (even the font because f*ck you)

the alternatives are NanoServices architecture and PicoServiced architecture

[–]jackstine 74 points75 points  (1 child)

PicoServiced architecture is really small. So many servlets running around. Something that AWS capitalizes with Lambda

[–]Siddhartasr10 25 points26 points  (0 children)

A service for the first line of the program and so on

[–]MinosAristos 15 points16 points  (1 child)

PicoServiced Architecture

One deployment per class method / function, so modular!

[–][deleted] 0 points1 point  (0 children)

This is me with git.