CarlHoerberg

Yes, we do use raft for leader election

yes, a bunch of older clusters were affected by this. They included an intermediate of USERTrust that was signed by AddTrust, clients that didn't check for alternate chains would then fail. We pushed the new chain (which now only includes the server cert and the Sectigo RSA cert), and dynamically reloaded the TLS listener in RabbitMQ, it should have solved it for most ppl, email support@cloudamqp.com if it didn't for you. We're sorry we didn't pushed this earlier. We were aware that the AddTrust would expire during the life time of the server certificate, but we assumed that all TLS client would find the valid chain regardless, that assumption was obviously wrong.

Lutfisk, yes, very much so

Where is the sole number used for authentication? We got the same number in Sweden but the number is not secret, you need it combination with something else like an ID, signature, digital signature etc.

Thanks for pointing that out! We would, of course, love to have female speakers on the summit. We had an open call for talks, which was promoted on the web, Twitter, newsletters etc., but there were only male speakers applying, unfortunately.

In the talks committee, Dormain Drewitz (who leads Product Marketing at Pivotal) and Lovisa Johansson (Marketing Manager / Software Developer at CloudAMQP), two female professionals highly experienced in RabbitMQ, was participating in choosing the speakers. In terms of the panel discussion, it will be lead by Dormain.

Lovisa is very skilled in RabbitMQ, and has written ebooks, technical documentation and tons of blog posts on the topic. However, she couldn’t participate as a speaker or in the panel discussion since she will have other commitments during the summit.

Diversity is a high priority for us, and we have a lot of females working behind the scenes as project leaders managing the summit.

This initial approach, at least, does not cache the intermediate CNAMEs nor does it care about the CNAME TTL values.

That's a total violation of the standard and will break A LOT of things. Example: my.domain.com -> CNAME ec2-1-2-3-4.aws.com 30s TTL -> A 1.2.3.4 30days TTL.

So Firefox will now cache my.domain.com to 1.2.3.4 for 30 days? When you update the record for my.domain.com the change today will be applied in 30s, but with this flawed heuristic it won't expire until after 30 days.

Setting up Dovecot (with master-master replication) and Postfix (+ spamassassin, dmarc, SPF) isn't too bad. There's a lot of dated guides out there though. Stick to the man pages as far as possible.

10k/s is no problem for RabbitMQ, even on aws t2 machines. Where did you get that from? 50k msgs/s is no problem on an aws c3.xlarge instance (single queue, auto-ack and transient messages).

Check out www.elephantsql.com, we provide managed PostgreSQL on GCE, AWS, Azure and Softlayer

(Most often you can pay AWS by wire transfer if you contact them)

Finally, it's crazy that they've haven't implemented this earlier, and why isn't it enabled by default, like on GCE? We've had for a long time an app that just polls the ec2 api and looks for impaired instances and then automatically restarts them. We have about 2-10 impaired/scheduled-for-reboot/on-deprecated hardware-instance per month so that app is quite a time-saver.

That's fixed in 33: http://msujaws.wordpress.com/2014/08/01/faster-and-snappier-...

True, just trying to balance the overly positive comments, without spending a lot of time laying out arguments.

I think it's awful. I only finished it because we're discussing it in a book circle.

Long time customers have had access to it since early May.. https://assets.digitalocean.com/email/ipv6-grandfathered.htm...

easiest way i've found is: RUNLEVEL=1 apt-get install ...

No, if I choose Sequel (http://sequel.jeremyevans.net) I want to use all the power it gives me, not some lowest common denominator.. Also not all projects needs models, you know, there's other data access patterns..

sinatra is more powerful than you maybe have realize..

sinatra/base, rack-urlmap and sequel, why would you want more fluff?

Do you have a reference backing that? I've only found information contradicting that, eg: http://support.microsoft.com/kb/318803

Ok, yes, in the case where you have to have all information on one page. Another way is of course to get that information in a ajax call, or open a SSE/Websocket connection to listen for events from the event bus. But there are of course cases where that's not feasible.

And in the case of auth systems what we typically do is to have a separate app for logins/authentication, then do simple SSO or domain cookie sharing and let each sub system handle the authorization.

My point is that not all SOA has to be as complicated as the article's. But if you go that way, yes, then all your points apply.

If you use a message queue system like RabbitMQ, and simply publish messages as JSON you have interfaces, authentication etc. done already. We have 17 different services internally, in four different languages, all communicating over AMQP with JSON messages.

(Disclosure: I'm owner of CloudAMQP - RabbitMQ as a Service, www.cloudamqp.com)

It depends how you do SOA. We try to publish "events" rather than to "call" another service and expect responses. We try to decide as much as possible in the service that publishes an event, so that information doesn't have to be returned. Other services act on that information.

Your kind of SOA sounds more like distributed RPC, which indeed is complicated.

We use SOA a lot, we have a RabbitMQ server/cluster in the middle who all services communicate via. We have applications written in Ruby, Go, Clojure and Node.js, all publishing and subscribing JSON messages.

Benefits over monolithic: New languages/techniques can be introduced at any stage, and used for what's best for. Applications can be isolated, and only do one thing, making the system much more reliable. Your web front doesn't have to down because you have a bug in the mailer app.

Benefits over HTTP: Not everything is web facing, workers etc doesn't need a full web stack. Services can be offline, without interrupting other services. You get load balancing and work queuing for free. Performance, 5000msgs/s with disk persistence is no problem for a low end RabbitMQ server. Great inspection capabilities with RabbitMQ's management interface.

Tip: Get away from a "RPC" mindset, think "events" instead. Let other services subscribe to events they should take action to. Decide as much as possible up front, in the application that publishes events, so that information doesn't have to be returned.

Disclosure: I'm the owner of CloudAMQP (www.cloudamqp.com), RabbitMQ as a Service. But have used SOA and RabbitMQ a lot longer, both for small and large projects.

We use Paymill for which we're very satisfied with. The initial paperwork isn't fun, but the experience is much better than all previous options for EU companies..

I believe that PayPal's new API is only available for american merchants.

Nice, then maybe I can get rid of some of the ~20 SIM cards I'm carrying around, and not having to research the mobile market for each new country I happen to pass by..

but encrypted..

exactly my experience too

the paymill paperwork is minimal. braintree wants a lot more papers (https://www.braintreepayments.com/tour/international) and has som hefty upfront costs.

OpenDNS still resolves the correct ip:s..