moca

5 ms·

1.
by moca 9y ago
Both Google and Microsoft have published their API design guidelines, which are very much RESTful. Both companies have applied their guidelines to broader set of products at very large scale. At least, we have not seen alternatives that wou
2.
by moca 10y ago
This guide has been in use since 2014, including recently launched Cloud Spanner API. Disclaimer: co-author of the design guide.
3.
by moca 10y ago
Many Google APIs were created before this guide. New APIs published at https://github.com/googleapis follow this guide. Having the same API available via both REST and gRPC is very valuable, as gRPC often provides 10x perfo
4.
by moca 10y ago
Thanks for the comment. The error handling chapter will be published in a few weeks. For now, you can reference https://github.com/googleapis/googleapis/blob/master/google/... . Disclaimer: I am one
5.
Google API Design Guide(cloud.google.com)
3 points by moca 10y ago|0 comments
6.
by moca 10y ago
The proxy is packaged as a docker image, it can run anywhere docker is supported. For performance and convenience, the proxy and the server typically run next to each other, but that is not required.
7.
by moca 10y ago
Have you considered to use a centralized configuration storage (such as S3 and anything else) with access control and audit trail? That is easier to update configs without restarting all the servers.
8.
by moca 10y ago
Agree. If you use any SDK built on top of Application Default Credentials library, it should work automatically and transparently across different environments. The complexity is handled by the library. [0] https://cloud.google.c
9.
by moca 11y ago
If we look at how much technologies have advanced over last decades, the economy produces more than enough output for basic needs, which can be distributed to everyone without much burden. We can simply offer basic income for everyone, then
10.
by moca 11y ago
For consumer applications, you are limited by the ecosystems, such Android or iOS or Windows, so you can't choose kernel anyway. For cloud applications, what is more important is the system architecture, not the kernel. If we assume do
11.
by moca 11y ago
A single disk seek takes a few milliseconds. If you need to do any kind of disk verification, it will take longer than a few milliseconds.
12.
Defining REST API using simple protobuf annotation(github.com)
2 points by moca 11y ago|0 comments
13.
by moca 12y ago
I have seen this kind of problems many times in real life. By start writing design doc and prototype code from very beginning, you demonstrate effort and progress. You most likely get hold of the project and eventually deliver it along with
14.
by moca 12y ago
SpaceX would drive the product and Google will be a great partner and investor. It is a good match. If Google drive the product, that would raise a lot of concerns across many governments - like EU - as if they didn't have enough probl
15.
Xiaomi's iPhone 6 Plus competitor doesn't rip off Apple(theverge.com)
1 points by moca 12y ago|0 comments
16.
by moca 12y ago
Your statement is incorrect. HTTP/2 essentially sends HTTP requests/responses through a multiplex channel. The semantics is nearly identical to HTTP/1.1. SPDY has approved it in real world for several years, and many major co
17.
by moca 12y ago
> Bandwidth is cheap. Bandwidth is just one problem. If you use HTTP/1.1 to download large files, you won't have much problem. If you try to design a memcache-like protocol based on HTTP/1.1, the result will be terrible. Y
18.
by moca 12y ago
I have used several Xiaomi products (phone, box, MIUI). I can say their product design and quality are very good. Obviously, they copied hardware design from Apple, but they have proved that they can build high quality products at very low
19.
by moca 12y ago
Among major companies, Apple did a better job with supporting old devices. Google Nexus devices become completely out of date after 2 years (too slow to run latest software, and too hard to get hardware repair support). Software wise, Apple
20.
by moca 12y ago
Java tried green thread since day one in 1995, and it never worked out well and was dropped long time ago (around 2000). Go did a good job with its gorountine at certain cost, for example embed Go library is much harder than C library, so G
21.
by moca 12y ago
Since iPhone 4, iPhone design seems going downhill. With the same display size, iPhone 6+ is much bigger and heavier than LG G3. Its quality is so much better than others, especially on camera and battery life.
22.
by moca 12y ago
Today Alibaba has more sales than eBay and Amazon combined. One important factor was Alibaba had enough capital to outrun competitors, considering it offered free service in its early years and how strong Tencent and Baidu were China. Jack
23.
by moca 12y ago
iOS apps use fixed layout, so they can't scale up/down with different display sizes. Since iOS only did double density once so far before iPhone 6 Plus, apps are quite easy to handle it. Android has way more variety, which is a pa
24.
by moca 12y ago
Android UI system still uses pixel in many places, such as MotionEvent.getX(). It should just use DIPs everywhere, which would significantly cut coding complexity.
25.
by moca 12y ago
I have worked with Internet services for many years. I think we have missed quite some opportunity to build great web app platform. For example, we could package web apps in .apk/.jar package, so they can run like native apps without w
26.
by moca 12y ago
TI stopped developing OMAP chip 2 years ago. The natural assumption would be the project was started before that. Due to the complex, it should take more than 2 years for a large company to develop it (startup might do it faster). NOTE: iPh
27.
by moca 12y ago
The reason is obvious. Moto must have worked on this thing for years, but couldn't make it work well enough. This is the first time that Moto or Google can build something that is marketable. It will take 1-2 generations to be really s
28.
by moca 12y ago
In a company like Amazon, only one person can push for such a product, eg Jeff Bezos himself. For whatever reason, he just liked the product idea. Very few people would appreciate such a product as sales number shows. It is just a worse ver
29.
by moca 12y ago
This redesign is for the sake of redesign, or promotion, or nothing. I don't see much, if any, value to a real user. Just waste of time.
30.
by moca 12y ago
It is easy to explain no manual control. Google will include insurance cost into the service itself. If there is any accident, Google's insurance plan will cover it. If there is manual control, the insurance cost will be a mess, since

More ›