Microservice Design Patterns article offer a view on the software patterns that could be used to build microservices. Clearly the proxy and aggregator patterns offer some structure in avoiding REST microservice’s overload from a user interface perspective.
This leads nicely to Ray Nicholus “The Future of Web Development – React, Falcor, and ES6” article, noting in particular the need to keep things “simple”, avoiding the unnecessary request overhead, large number of requests, and needlessly large response payloads, which in a trading application can kill performance/latency/user experience, and thus the clients. You won’t get much argument around React from myself, and likewise the Falcor I find sensible, since I used such concepts on a number of projects back in time (too long ago). Webpack – agree again. Overall a good article.
Moving on to “Do Good Microservices Architectures Spell the Death of the Enterprise Service Bus?” which provides a good list of high level challenges of Microservices. Its nice to see Swagger mentioned around contracts. Likewise a nice callout to in-memory data grids, and not just the classic data cache.
Microservices are independent, scalable services. A modern architecture uses a scalable platform, which allows automating deployment of different technologies / services / applications independently. Use the tool(s) of your choice to define service contracts, implement (micro)services and service discovery, automate independent and scalable deployment. Coordinate different (micro)services and react proactively in real time to events by doing event correlation in-memory. That is how you create a good microservices architecture.