A lot can be thought, written, and defined, but, without a practical test, nothing can be taken as real. Of course, venturing into a new ecosystem is a big risk, so, it is best to create a prototype to verify if all concepts, experiments, and patterns chosen can be applied efficiently.
A good tip for creating a prototype is to choose the smallest and least complex field possible; a field which, effectively, does not represent a risk to the application as a whole.
Get Microservice Patterns and Best Practices now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now