1,617 karma · joined December 7, 2015
> Ably is a Pub/Sub messaging platform that companies can use to develop realtime features in their products.
At this time, https://status.ably.com/ is reporting all green.
Althought their entire website is returning 500 errors, including the blog.
It is very hard not to point the irony of the situation.
In general I would not be so critic, but this is a company claiming to run highly available, mission critical distributed computing systems. Yet, they publish a popular blog article and it brings down their enire web presence?
I don't like to speak in negatives so I won't elaborate, but basically I've had a very hard time using it and it made work miserable. Besides the shiny UI, there was literally nothing to make a devops team's work easier. Simply accessing a failed job log output was hard.
I prefer gitlab-ci because I already use gitlab and the integration is nice. For a pure CI system I would use drone.io if I was not already using gitlab.
After being burnt badly by the "official" docker auto-updates breaking stuff a few times, I've had enough and seeked a better solution. Turns out it was already there, no 3rd party package repos required.
Linux distros package managers go to very great length not to break users' work environments. They keep things working, secure and stable, and I am very grateful for it.
Our project is a security centric router/firewall/wifi AP with cloud management.
We do have a rogue wifi monitoring feature, but your approach and execution seems so miles ahead from what we're doing that I'm highly tempted to scrap it and integrate nzyme instead.
I am thinking that we could remotely configure/dedicate some radios to an nzyme process embedded in our firmware.
We just had the go ahead from our main sponsor to fully open-source our project so I'll be in touch!
What we've done for the past few years is trigger async fetches in componentWillMount on the server and perform multiple renderToString.
This requires some instrumentation so you can monitor that all the data has loaded and your tree is fully rendered.
Removing componentWillMount will force us to rewrite everything to the suspense API. I hope that transition won't cause too many headaches.
Drew a face and it proposes ovens and random jitters as closest matches???
- Redundancy. Platforms like k8s and other PaaS can distribute instances of the same apps to multiple hosts / availability zones.
- Zero downtime deployment. Spin up the new version in a container, have both previous and new version running concurrently, then start routing traffic to the new app.
- Standardization. Settling on a container type to run all your apps makes for great dev and ops relationships.
- Immutable code. Know exactly which version is running in production and be confident it can't be changed manually.
You can listen for localStorage changes in all your tabs. When it changes, force a page reload or similar.
Edit: typos
With something like Avatar-JS [1] you can even run some NodeJS apps without modifications on the JVM.
I have moved dockerized apps to public cloud CF to on-prem CF. It all worked because the apps where stateless to begin with. Pivotal appropriating all the merit of easy migration of stateless apps is dishonest at best.
Stateless apps are easy to move. They can be moved from CF to Kubernetes to ECS to Heroku.
Now, let's talk about the state, because that's where the real problem and the lock-in might be?
aws elb support http and https termination, and can even provide free SSL certs. Azure's is tcp/udp only.
And the new aws Application load balancers offer even more features.
So it depends on your use-case.