This is a truly remarkable video. I sometimes wish, and I am not a fanboy, that Steve Jobs would have moved into academia at some point and preserved much more of his experience and knowledge.
It is fascinating to hear Steve talk about strategy, corporate culture, marketing, and many other subjects. The video is from early 1992 and in my opinion many points are still bleeding edge today.
For me the bottom line of this video is: Microservices come with a huge amount of challenges, that you do not have with a monolith. Chris covers a lot of topics, each of which deserve a number of dedicated videos.
Here is how to get started with Continuous Delivery
I recently had the need to compile Git on a CentOS 6 system, because the available version (v1.7.1) did not support the ls-remote command used by the Jenkins Git plugin. The various posts I found via Google were missing a crucial prerequisite, hence this short post.
yum remove git
sudo yum install libcurl-devel zlib-devel asciidoc openssl-devel xmlto
gzip -dc <FILE> | tar -xvf -
make configure ./configure --prefix=/usr make all sudo make install install-doc install-html
And that should be it.
Sam Newman and Martin Fowler in a conversation-style video that looks at Microservices in a non-bullshit way. Must watch!
A typical (in the best possible sense) video from Simon Brown. Best part for me was modelling and that a common structure is more important than the notation itself.
The definitive video on Microservices, as far as I’m concerned. No marketing bullshit, no misguided “stateless-hello world-crap”, but a concise and applicable set of criteria. It is also worth noting, that overall/in general Dave prefers a service-oriented monolithic architecture. I can’t express how great this video is to describe the real core of the idea of Microservices. Please take the time to watch!
Brilliant video with lots of references to good stuff for reading.
Although I have been a Linux person since 1995, I have come to like FreeBSD a lot. Primarily because two of my major systems are based on it. As my firewall I have been using pfSense for a number of years, and for storage it is FreeNAS. And both have never let me down, neither in terms of stability nor regarding their functionality.
Now the company behind FreeNAS (iXsystems) has announced a while ago, that they will move to Linux as the underlying operating system for their future core product. I am not sure I welcome this change that much. I can understand that simply for available know-how iXsystems want to do this switch. Plus the hardware vendor support is obviously broader and the community also does their part in testing. But, with some level of exaggeration, Linux (not the kernel but adjacent things like systemd) has become kind-of the JavaScript framework of *nix systems. What I mean by that is that I personally perceive the rate at which things are re-done as too high for my liking. Just like every year multiple JavaScript frameworks appear that do the same thing as twenty others, just differently.
While there is merit to improving things, stability is often more important. And stability not only means that things work as expected. But also the rate of change is a factor. If a new framework saves me 20% development time that sounds great. But in the enterprise evolution, and by that investment protection, is typically what gets you the much better ROI. Because the 20% development improvement are more than eaten up by effort in other areas (esp. operations).
There seems to be, at least partly induced by the relatively powerful merge-capabilities of Git, a trend back to using feature branches in distributed development. Since most of the folks I heard supporting this, are not super-senior it appears that feature branches seem the more obvious choice. Dave Farley, who is basically one of the inventors of CI/CD makes a very compelling argument against features branches in this video. Please watch!