Hello to the experts and authors of the Microservices in Action book:
Congratulations on your book launch, couldn't be a good time than now to ask a few questions pertaining to what the book title speaks for:
Currently, there seems to be a sudden boom & hype about the newest architectural style for designing modular and real-time applications, e.g: Netflix, being the most popular one.
As a novice to microservices, who has less information about this new architectural style, I have a few questions:
1.) When should one determine the need for adopting microservices architecture?
2.) Does security come at stake when we consider several small(not necessarily small) components talking to each other?
Because in the typical monolithic architecture style, the security is application wide bounded; in Microservices case, do we need to enforce security to all the 'n' components involved?
If yes, then how is the redundancy of writing security code managed? Suppose a banking application which needs to be highly secure at all levels?
3.) What care should be taken when transforming a monolithically developed application running for a couple of years to a microservices architecture? Should the entire wheel be re-invented? Or can we re-use the existing parts whilst designing?
Looking forward to your answers on these and the book as well.
P.S. Please forgive me if my questions are too naive or vague in any way.
That's my roommate. He's kinda weird, but he always pays his half of the rent. And he gave me this tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java