If they are announcing things like a brand new hypervisor ahead of re:Invent one wonders what they are saving for the main event...is it too much to hope for managed Kubernetes?
509 karma · joined September 3, 2015
If they are announcing things like a brand new hypervisor ahead of re:Invent one wonders what they are saving for the main event...is it too much to hope for managed Kubernetes?
As an end-user the first thing I want to do before reporting a bug is search and see if it has already been reported or if it is being worked on and when it is expected to be released. If I was told that I had to dig through mailing list I would probably just stop before I even started.
> Can you explain why you think a mailing list is less efficient than a bug tracker?
As a bug reporter, I want a friendly way efficiently search and filter existing bugs based on status, version, subsystem, etc. I also want to be able to subscribe to a specific bug to get updates. Maybe you guys have some way to get all those features from a mailing list, but new users certainly won't have a clue.
As a developer I want to be able to easily tag, filter, assign and triage bugs. Assign priorities and associate them with releases and pull requests. I also want to be able to do high level reporting.
A mailing list hardly seems like an efficient method for tracking bugs unless a major part of the efficiency is reducing signal to noise by make it more difficult for non-developer or non-paying users to file bugs
It would have been nice if they at least mentioned it in the article since Selenium is such a popular browser automation tool. They do in fact mention it on the README page for headless chromium.
[1] https://github.com/SeleniumHQ/selenium/wiki/ChromeDriver
[2] https://sites.google.com/a/chromium.org/chromedriver/home
[3] https://chromium.googlesource.com/chromium/src/+/lkgr/headle...
Straight up MySQL RDS is still cheaper at approx $25/mo for db.t2.small and $12.50/mo for a db.t2.micro instance (not supported by Aurora). But since Aurora data is stored redundantly and recovery happens automatically, even a single instance setup is probably better that what a lot of people are running now.
AWS claims automated recovery times of 15 mins for a single instance and less than 60 sec for a Multi-AZ configuration[1]. Seems like this entry level Aurora instance should be a no-brainer for anyone running MySQL RDS on a db.t2.small instance in a production-like environment today without high-availibility.
Full pricing list here: https://aws.amazon.com/rds/aurora/pricing/ [1] https://aws.amazon.com/rds/aurora/faqs/
I have tried kappa (Python) and node-lambda (Node.js), and serverless works better than both of them, is more frequently updated (Lambda and API Gateway themselves change frequently), supports more languages (I have used it with Java, Python and Node.js) and has a much larger, more active community.
The API gateway support is pretty simple and solid, and they also allow you to use cloud formation rules directly so it is very flexible.
Then I refreshed and the event disappeared altogether.
[1] https://phd.aws.amazon.com/phd/home?region=us-east-1#/dashbo...
"500 The server encountered an error processing your request." message
This type of opaque pricing normally annoys me, but they were recently acquired by Google so I expect the pricing to eventually become more transparent and most likely be fairly reasonable.
The api.ai UI for building interactions looks way more approachable and developer friendly. On top of that it looks like they are building out support for multiple platforms (Slack, FB, Alexa, Telegram) so you can (maybe) have a central integration point for your all your chat apps. Some of the integrations look very basic though.
The biggest downsides are that I have never heard of these api.ai guys before and the pricing beyond their free tier (1 query/sec) requires you to contact them, yuck.
Edit: Looks like I spoke too soon. Apparently they were acquired by Google recently[1]. I was wondering why Google was making this startup so central to their product. Now they just need to be more transparent on pricing, but I guess they are testing the waters right now.
As with most ideas there is room for different projects and approaches and the landscape is constantly changing so it will be hard to tell which will survive. Even API Gateway's recent addition of the proxy integration feature makes things a lot simpler and probably made some code from all these frameworks less relevant.
So yes the internal AWS "team" has advantages in terms of being able to post to their blog and perhaps being privy to internal developments before you are, but that is just the way it is. Looking at GitHub the team appears to really just be one person https://github.com/awslabs/chalice/graphs/contributors. I just think we should have an open mind and allow for the possibility that they are trying to explore their own ideas and address what they perceive as their customers' needs rather than assume they are trying to crush all similar projects in the name of corporate greed.
With Step Functions it is now trivial for me to write a simple Python lambda to do the HTTP request and then have the state machine deal with retrying with an exponential backoff (30min, 2hr, 8hr) for as long as I want.
If you wrote that by hand you would either need a long running process or you would need to manage scheduling and state management yourself.
I was actually planning on doing something like this with lambda, but I was basically just going hack something together to fire the Lambda multiple times per day using CloudWatch Events and then use DynamoDB to keep track of whether or not I had already succeeded. This is much more elegant and robust and you get a visual overview and execution history for free.
(1) Quickly get a visual overview of all your executions
(2) See how many workflows failed
(3) Drill down and see which specific step failed and the data that might have triggered the failure
(4) re-run specific workflows
It provides built in error handling, retries/backoff, and parallelization. These are all things you could code yourself, but at some point you would have built a workflow system. Not to mention that the infrastructure of the workflow system itself is managed for you, so you don't have to worry about that going down. You can write workflows that execute over days, weeks or months and not worry about what happens if your server goes down.It would also come in handy for mutli-language workflows. If your were interacting with a variety of third party APIs that had SDKs in different languages, you could quickly string together a Python Lambda, Java Lambda and some .NET code that used the long polling API.
It would be nice if it integrated seamlessly with Cloudwatch and X-Ray to provide a unified view of logging and tracing right from the same interface.
I also expect a more seamless integration with AWS Batch at some point. Could be useful for chaining together multiple independently maintained batch processes (video conversion, resizing, publish to youtube).
I personally use SWF for a 10 step e-commerce workflow that calls multiple API. It works great, but I could have developed it much more quickly using Step Functions if it were available at the time.
I was hoping they would do something like this, working with SWF has always felt unnecessarily complicated. The Java Flow Framework just felt like an awkward abstraction to me, but this makes a lot more sense.
Combine this with their new AWS Batch service and I think people are going to save countless man hours that would have otherwise been spent working on repetitive, undifferentiated code.
FYI it is also possible to go directly from the API Gateway to S3 without going thru Lambda
That seems a bit reactionary. A large number of the bars will have the same expiration date even if they were produced in different batches or facilities.
This whole piece seems to be designed to stir up emotions rather than provide real analysis. It is fine to express concern when people are getting sick, but this seems more like a attack. The default assumption seems to be that the Soylent team is hiding something, which does not seem consistent with Rosa Labs' previous disclosures about production issues.
Anyway I have been eating bars from a box with the same labeling (B1-00CAR BEST BY 1966 14JUL17 0716) for weeks with no ill effects. Rather than throwing all their product away if someone is worried they can try consuming a small portion of a bar first and then wait to see if there are any ill effects.
I have evaluated a number of different options and I am about to start using Sift Science[1]. In addition to using standard ip address/email based information they also use social data and machine learning to identify fraud.
Their API/data model is the most well thought out and comprehensive one that I have come across and they allow you to back-fill up to 12 months of historical data for free to help improve your detection rates. They also have a console to assist with optional manual review workflows and store integration apis to allow full automation.
On top of all that they offer scalable pricing that works for both large and small business at 6c per transaction.
Obviously I can't vouch for their results yet, but what I have seen so far looks pretty good. If you have a fraud issue you should at least check them out.
Namesilo keeps pricing very low, simple and straightforward ($8.99/yr for .com). I haven't had any problems with them so far.
Stay far away from GoDaddy, they try and lure you in with discounted pricing then jack up the price on certain features later on. They are constantly trying to up sell you something else and they make transferring your domain away unnecessarily complex. At least that was the case when I last used them.
She made a comment in the Verge forums clarifying that she did in fact have his permission.
http://www.theverge.com/2015/9/2/9247915/addiction-feature#3...