Amazon Vendor Central only has support for EDI (at least in the UK) - as in EDIFACT files sent over FTP.
If you want to do business with them you either need to talk that or be comfortable farming out to a 3rd party (I'm 1 day into a project where I'm finding all this out, and the hell of EDI file formats).
I'll prefix my comment by saying I'm someone who is more on the sysadmin side of the scale of things. My code isn't pretty, but it generally works well enough to get the job done. I'm learning (probably the most important thing, I guess).
Contexts are one of things that I felt the same about. Until I tried really using them, rather than stressing over whether or not I was using them properly.
I made the mistake of trying to think of them as microservices, which bogged me down and for my purposes was complete overkill. I've now reached a kind of happy medium, which I've realised that I really should have already been using. I've kinda realised I suck at api design. And for that I'm very thankful to the phoenix team, because it feels like I'm learning.
I feel dumb not even having looked whether or not anyone actually produced cloned 10G cards.
Have you had any success with them yourself? Is there any data or resource on how trust worthy these clones are? Tempted to order a couple for testing at home with, at some point...
protobuf sounds attractive, but (unless I've missed something in protobuf's implementation), but out of the box you have 2 issues:
1. Protobuf doesn't/can't deal with fragmentation - so you'd have to ensure your protobufs are small enough to fit inside a UDP packet
2. Without a wrapper you couldn't put multiple small protobufs into a single UDP packet?
Both things are fixable by wrapping protobuf, but I suppose if you're trying to get something as small as possible, can you actually just do better by avoiding protobuf in the first place (I guess the answer is yes?)
I understood it as using protobuf's interface definitions as as an integration point, not necessarily protobuf's exact wire format and everything below it that comes out-of-the-box (like TCP and below) in the default client.
protobuf as a structure serialization/deserialization library shouldn't have the responsibility for delta calculations in the first place. Once the application decides what the delta is, it can use protobuf or anything else to encode and transmit that.
I believe the point is that you have CoreOS hidden behind a firewall you can control, therefore you only have ssh open to sources you permit, you use a bastion host, etc.
So a Ubuntu server in front of CoreOS works... :D ;) I'm thinking of a small cloud setup like on DigitalOcean were you need ssh into the CoreOS server.
Dumb question, but how did he start playing Dota 2 at the age of 7? Surely thats a mis-print - it's not been out that long? Development only started in 2009...
Dota was originally a custom map for the Blizzard game Warcraft III released circa 2005. In 2011 Valve hired the developer of the custom map to make a full standalone game and that became Dota 2. Most players (including me) played the original game before shifting to Dota 2.
They probably meant Dota 1. Dota 2 is an HD remake of Dota1 with the exact same units and game mechanics so most players consider both games to be the same thing.
Amazon Vendor Central only has support for EDI (at least in the UK) - as in EDIFACT files sent over FTP.
If you want to do business with them you either need to talk that or be comfortable farming out to a 3rd party (I'm 1 day into a project where I'm finding all this out, and the hell of EDI file formats).