Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pitää alkaa hahmottaa kokoavia rajapintoja #17

Open
kyyberi opened this issue May 16, 2015 · 0 comments
Open

Pitää alkaa hahmottaa kokoavia rajapintoja #17

kyyberi opened this issue May 16, 2015 · 0 comments

Comments

@kyyberi
Copy link
Member

kyyberi commented May 16, 2015

An application client, such as a native mobile application, could make RESTful HTTP requests to the individual services
On the surface this might seem attractive. However, there is likely to be a significant mismatch in granularity between the APIs of the individual services and data required by the clients. For example, displaying one web page could potentially require calls to large numbers of services. Amazon.com, for example, describes how some pages require calls to 100+ services. Making that many requests, even over a high-speed internet connection, let alone a lower-bandwidth, higher-latency mobile network, would be very inefficient and result in a poor user experience.

A much better approach is for clients to make a small number of requests per-page, perhaps as few as one, over the Internet to a front-end server known as an API gateway

3fig5

http://www.infoq.com/articles/microservices-intro

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant