812 karma · joined May 8, 2008
Probably should have searched first :)
https://www.aweber.com/careers.htm
AWeber is an email marketing platform that allows 100,000+ small businesses and entrepreneurs to create and send emails people love. We're consistently voted one of the top companies to work for in PA and have a ton of benefits.
We're looking for a full-time (preferably onsite but remote ok for the right candidate) Senior DBA to help oversee our large Postgres infrastructure (and other DB technologies as well).
For more info on this role, visit https://www.aweber.com/careers-application.htm?gh_jid=150505...
We have a handful of other onsite-only engineering related roles open as well: https://www.aweber.com/careers-engineering.htm
Stack: Python (Async & Tornado), React, Swift, Kotlin, Postgres, Redis, DynamoDB, AWS, Ansible, Linux, Docker, K8s and a fair amount of other stuff too.
FWIW CloudFormation added YAML, which was a vast improvement to usability IMO over where they started. Want CloudFormation to support something else? Lobby through your AWS account rep for what you want supported.
Preference is preference. Stop acting like it's not. This page might have been "Nobody wants to use VI" or "Nobody wants to use Emacs" or "Nobody wants to use [insert thing I hate here]"
io:fwrite(string:join(string:tokens("Hello,How,Are,You,Today",","),".")).
This is the opposite direction of what RedHat should have done.
I was hoping this was a acquisition to move RedHat's technology stack moving forward and instead it's one to move an innovative and solid platform backward.
Acquire, assimilate and kill off competition, just like other RedHat acquisitions before it. :(
Oh and the FU on all of our existing integration use is cute.
They should have released it as a UI improvement for HipChat, not a whole new ecosystem.
Great writeup! One of the issues I've run into with LISTEN/NOTIFY is the fact that it's not transaction safe. ie if you call NOTIFY and then encounter an error causing a rollback, you can't undo the NOTIFY.
I ended up building a system on top of PgQ (https://wiki.postgresql.org/wiki/SkyTools#PgQ) called Mikkoo (https://github.com/gmr/mikkoo#mikkoo) that uses RabbitMQ to talk with the distributed apps that needed to know about the transaction log. Might be helpful if you end up running into transactional issues with your use of LISTEN/NOTIFY.
Heck, it is possible even remove images from the docker repository without corrupting it, just not from a single API endpoint. FWIW I think that it is a big failing of the v2 repository project to not have that functionality from the get go.
It's also worth noting that I've only run Docker in production using CoreOS and Amazon's ECS AMI. Both have their drawbacks, but nothing so dramatic as to keep me from recommending Docker in production for "cattle" style applications.
You're absolutely correct re load balancing for high-performance/ceilings/etc. It's not a huge issue for our use, but I can how it can be for others. In my previous environment, for example, it was absolutely critical.
I'm sure this tool isn't for everyone, for us it was about making cluster startup easier and letting RabbitMQ handle that instead of a configuration management system like Chef/etc.
For example, our test environment is torn down every night on an autoscaling schedule and rebuilt in the morning. Not having to worry about config management for starting up a new RabbitMQ cluster on demand is a nice feature. :)
Thanks for pointing out the clear (and accurate) concerns one must consider when running RabbitMQ @ scale. It sounds your experiences are similar to my own with where the gotchas can be.
This is the first version that has the destructive action of removing nodes from a cluster when they disappear and even then it's behind two different config variables: One to turn cluster health checking on and the other to actually do something when bad nodes are noticed. Bad nodes being nodes that are no longer visible in the service discovery backend and no longer pingable by the cluster.
An Erlang based AWS client that intends to be a thin wrapper for httpc. What makes it different than other Erlang based AWS clients is configuration and credentialing. Config and credentials can be set in the app config, OS environment variables, AWS CLI configuration files, or by accessing the AWS EC2 Instance Metadata API.
While they say it will be available across all of the platforms available today, noticeably absent in the enumerated list are OSX and Linux.
Seems like it's for table schema snapshotting in a database without any external storage.
Browsing through the code, I see that it's highly table centric using SQLAlchemy.