I came kind of  late to this discussion so you guys might have already talked about this, please ignore if that is the case. 
I see that in the goals page there is a bunch of work regarding current projects but there is little mentioning of the 'background work' needed to deploy services.  It seems that the work of building the infrastructure should be called out explicitly.

For example: 

1. Transport: have we chosen what is it going to be our transport protocol? as in json-rpc, protocol buffers...

2. Authentication: are services for internal consumption only (and thus inside our firewall) or do they provide an authentication scheme?

3. Logging: How would you follow requests across services, or at least, follow the jump from client to server?


5.Testing (version aware)

6.Client Configs, how does the client know where services are?

7.Code generation from service api descriptor 

On Thu, Jun 5, 2014 at 7:21 PM, Gabriel Wicke <gwicke@wikimedia.org> wrote:
Hi all,

Matt & I have published our draft goals for the nascent Services team [1] at


Your feedback would be much appreciated.



[1]: https://www.mediawiki.org/wiki/Services

Ops mailing list