Vending machines in Japan seem to carry pretty much anything. It's surprising what they can come up with.

Like vending machines with live crab.

I would suggest: _Aardvark007

But important parts are missing.

Some examples:
- AzureAD, specifically ACS
- Site Recovery for disaster recovery

These are all online services with no buy/download equivalent from Microsoft.

Let me be clear: what applies to Azure as a foreigner applies also to Amazon/AWS, Google, Rackspace, IBM/SoftLayer, CenturyLink, DigitalOcean, Vultr, Linode, PeerOne or any other US-based company (even if they run the service in Europe for example).

But I noticed there are others in the world, for example on the OpenStack Marketplace:
http://www.openstack.org/marke...

I doubt it. They are in the business of selling products and services, they don't care what they can sell. They are a business trying to make money and stay relevant.

If running a porn streaming service wouldn't damage their image and was something they thought they knew how to run well and make good money on, I'm sure they would just add it to their list of services.

Now to be a bit more specific, of course they want your data. You see this happening especially on the consumer side.

For example: where can I get a copy of SkyDrive/OneDrive/whatever which I can run on my own systems ?

Anyway, I can't use Azure, I'm a foreigner:
http://media.ccc.de/browse/con...

I would think the number of languages magic number can be slightly higher if you have more development teams/microservices.

What I do know Amazon has a maximum size per development team/microservice: 2 pizza's
https://blog.bufferapp.com/sma...

I read some companies have a policy that the people developing the microservice should also develop the client library for that microservice.

So in that case if you add more languages to an organization, you'll add a lot more overhead (every team would have to have at least one member that knows each language used in the origination, or at least the language of the other team which wants to talk to the microservice).

But I guess I was late with my comment, but I didn't get any extra points for it. ;-)

You know, I don't always have time to keep an eye on what is going on the industry and lots of information/knowledge is spread around all over the place. But it only takes a few months to figure this stuff out. ;-)

As I mentioned above, it's not so much about the language you use it's about applying it to the right task.

node.js might or might not apply to what you need.

You see some companies do:
Node.js here because we got a good templating system, Go for this new part and Erlang for that other part because a really good open source system X already exists for that and Java for that other part because of open source library Y.

So it's very much about seperation of concerns and using the best tool (read: language and existing other libraries or databases) for the task.

The other part is:
Deploying different services seperately (don't let deployment/update of one service depend on the deployment of an other). That is why different services don't share their databases. So they can be updated seperately.

In larger companies, like Netflix, they put a seperate team on every microservice. They are completely self-organising, like a little startup or something like that. They choose the best tools for the microservice they are supposed to build and develop further.

Actually, you might be surprised but something else has been going on for years.

Let's have a look at what a company like Wallmart is doing. They replaced part of their infrastructure with node.js.

If you look at what they are doing is: they are replacing not the backend systems, they are replacing the user-facing/HTML-generating/CSS-generating/AJAX-talking/JSON-generating/whatever-it-does parts of the system with node.js. So node.js talks to the backend systems on one side and the browser on the other side.

Wallmart even have open source projects releasing and collaborating on the code they use:
http://hapijs.com/

Let's take an other example. They already made that transition earlier than Wallmart. Can I say they are also a house hold name ? Because that would be Paypal:
http://www.youtube.com/watch?v...

So now they can do frequent changes to the user-facing websites in hours, maybe even minutes. Instead of the 6 week update cycle they had with Java.

These are just examples of companies, but you can see what they are doing and hopefully you can also imagine why that makes sense.

Because now the webdevelopers deal with everything that talks to the client (browser) and the other teams create webservices. It's a good seperation of concerns.

Just in case you need a diagram, here is an article about it:

http://www.nczonline.net/blog/...

Then a couple of years later, this old concept of Service Oriented Architecture and the Unix-philosophy of single purpose programs was starting to be applied to this new 'cloud thing'.

They call it microservices now:

https://www.youtube.com/watch?...

You might have heared what Netflix has been doing in that space.

So the result is:

Languages are now competing which each other because you are building microservices and the protocols are pretty much standardized (HTTP, JSON, REST).

This means, languages get used for what they are best suited for.

And if they don't fit. You just rewrite that microservice in an other language. These code-bases are very small. And the processes itself are usually stateless.

All the data is stored in the data-store.

This means you can do this 'webscale' thing with your stateless microservice, because you can start as many of them as you need. All you need to do is put a bunch
of loadbalancers in front which disperse the requests over these other service specific processes.

Most of the time these microservices are just a single process, a daemon. Some use Docker or other containers to deploy them. Microsoft is now building the same for Windows.

Sometimes they include a webserver like nginx.

The same is happening to databases, NoSQL and SQL like.

You need to create a microservice that handles login ? You give it a seperate datastore, maybe you think LDAP is a good idea, who knows.

You need to build a microservice which handles checkout ? You give it a seperate datastore too.

You need to build a microservice which stores the session-information, yep, that too is a seperate microservice, it might be using .

And remember: that one microservice is the only service talking to that data-store.

Funny you should mention: project-manager.

You know, it turns out, smart people don't need any management. They can manage themselves. Management really doesn't add much value. The more complex the problems get, it's best to let the poeple working on the problem decice how to work on the problem.

Here is an example of bank, yes bank, which got rid of all the project managers:

https://www.youtube.com/watch?...

Some people might call all these things: devops, agile, cloud, software-defined-whatever and whatever else, but I think you might get the idea of what is going on.

Ahh, cool, didn't know nmap included that.

I know, that is why I mentioned:

"Let's look at HTTP, because this is a HTTP/2 article."

Anyway, for those that don't know:

echo -en "MAIL FROM:\nRCPT TO:\nDATA\nSubject: test messsage\n\ntest message body\n\n.\nquit\n" | openssl s_client -host gmail-smtp-in.l.google.com. -port 25 -starttls smtp -ign_eof

Voting is completely useless without fixing the gerrymandering.

Most of the the electections per state for the coming couple of elections are already known.

Just ask Kimball Brace.

Yes, HTTP/2 is a multipllexing binary framing layer, but it has all the same semantics of HTTP/1.x on top.

HTTP/2 is 'just' an optimization. So if your webserver supports HTTP/1.x and HTTP/2 then you can still use telnet to check whatever you want and it should give the same result as HTTP/2.

But you also have to remember:
The IETF which is the group of people who design the Internet protocol made this statement:
https://www.iab.org/2014/11/14...

"Newly designed protocols should prefer encryption to cleartext operation."

The W3C made a similar statement, there are also drafts with the intention to moving to HTTPS by default.

So it is all moving to TLS protocols like HTTPS or STARTTLS for SMTP anyway. Those are clearly not text protocol either.

So even if you want to interact with the text protocol used inside that TLS-encrypted connection, you'll need to use a tool because netcat or telnet won't cut it.

Let's look at HTTP, because this is a HTTP/2 article.

That tool could be the openssl s_client, but as you can see that is kind of cumbersome:
echo -en "HEAD / HTTP/1.1\nHost: slashdot.org\nConnection: close\n\n" | openssl s_client -ign_eof -host slashdot.org -port 443 -servername slashdot.org

But I suggest you just use:
curl -I https://slashdot.org/

The main developer for cURL works for Mozilla these days and is one of the people working on the HTTP/2 implementation in Firefox and is writing a document explaining HTTP/2: http://daniel.haxx.se/http2/
So as you would expect Curl supports HTTP/2:
https://github.com/http2/http2...

Basically every browser include 'developer tools' which will also let you see the headers and everything else you are used from HTTP/1.x.

I would rather see we all move to using encrypted protocols then that we can still use telnet.

My guess would be:

Microsoft is 'helping' Cyanogen to add some kind of cloud service.

Basically, putting you data in the Microsoft cloud.

I assume Cyanogen doesn't mind, because it's optional.

Well, that is my guess.

Yes, it's a really hard.

Lots of people have tried, for years now, they've all failed:

http://media.ccc.de/browse/con...

Things that might look good in theory still turn out to be a big fail in practise. Even just getting the implementations right is really, really hard.

Using a blockchain will probably fail too.

Remember if we knew how to make Bitcoin or Darkcoin/Darkwallet/Darksend/Coinjoin/etc. really, really good anonymous, we would have already done it.

I think this is a good sign for a differerent reason.

We all know OpenSSL could be a lot better. Supposedly they got more funding.

If they are busy finding and fixing bugs that's could be a good thing.