Baan still exists as Infor ERP Ln
60 karma · joined July 9, 2014
Baan still exists as Infor ERP Ln
Also any reason to believe that the tweet was true? (I’m not on twitter so i don’t have any context for the veracity of the source)
I'm married to an Architect, it bugs them too.
In most states - Legally they can't call themselves Architects until they've passed the AREs. You can't take the AREs until you have enough IDP hours (which takes about 3 years). You can't start IDP unless you have a Masters (or more recently a "professional bachelors"). Oh, and you have to take a new test for every state / country you want to practice Architecture in (Reciprocity is getting better but not quickly)
So it's that sense that they have to scratch and claw to get the title where we can just sort of make it up that bugs them.
I think we should switch to a different title scheme. I'm going to be a Doctor of Site Reliability (you know since I'm already doing operations....)
100% agree with you there.
> It mostly just keeps them even with Kubernetes at best. And an imitation of it at worst.
Personally, when I looked at kubernetes, mesos, etc and saw the xml hell that i'd be living in and said "no way".
If i have to run something as complex as those to have docker then it's not worth it to me.
When I look at the new docker swarm stuff. For the first time I think that docker is a viable thing (assuming it all works). because I'm not adding additional complexity to get my docker simplicity.
I'm saying that, if you want, you CAN make it guarantee that a container will be rescheduled to the same host. (or a controlled level of hosts).
I don't think it's docker's responsibility to solve database clustering.
And, as I said, I'm not advocating running a production DB in docker. But I can see a way that you may be able to.
Not saying that's a good idea, but it is getting closer.
You could, for example, have a node that's only for DBs that has volumes on it. You could then use DRBD on the host to clone that data to a secondary node. then in the event that node 1 dies swarm would bring the DB up on node2.
With the mesh network stuff they've added the endpoint would remain the same, so all your apps would need to do would be re-connect.
Yes the SyFy Mini-Series is more true to the book, but their pronunciations make it unbearable to watch for me. "Hark-e-nin" vs "Har-ko-nin" drives me up the wall.
Another thing I love about it is how surreal Lynch creates the future. To me it's one of the most immersive sci-fi movies that really takes you out of this reality and into it's own and it does it with minimal flash and special effects.
The Guild navigators are gross and amazing. The Lynch Baron Harkonin is possibly my favourite Sci-fi villain of all time.
The info I have came from a conversation with an AWS Solutions Architect.
It's a couple of years old, but based on my experience it's still true today.
We were using a Non-AWS DNS resolver (aka Google) and we would often get dns resolution errors despite our NAT not being remotely taxed by the traffic.
I only use Atom for coding and vim for just about everything else.
The most difficult part for me is that i'll open a file in vim and then consciously go "no" <close it> and fire it up in one of the other editors.
Why? because I like to keep my vim more clean. I've seen some of the really complex vim configs out there and they just didn't "do it" for me.
So if i want complex things like syntax highlighting I go with Atom.
Whether it's accurate or not, people associate Docker with the functionality if facilitates. (i.e., cgroups, namespaces, etc.) so i think it's valid to show the performance impact of running an application from within docker.
Based on my data, they're not 1:1 native performance. I suggest you consider the data before dismissing it.
I've updated the blog post to specify that since it was obviously unclear.
Also, this test wasn't meant to be scientific. I'm not selling docker, postgres or digital ocean, just satisfying a personal curiosity.
Benchmarks are touchy things in general, I understand that.
I published the results and I'd love to see someone publish conflicting results, or verify them. I've tried to be as transparent as possible.
I would see it possible that the pre-configured Digital Ocean machine favors docker processes over non-docker somehow.
The 3 docker conditions where No flags, --volume /.../, --volume /.../ --net=host
I'm the author of the blog post.
I started the container with --volume in the case of "docker with no virtual I/O"
Which is the same as setting VOLUME in your Dockerfile.