One of the more interesting data points to come out of our State of Application Delivery 2015 was the overwhelming importance placed on availability - even over security. When respondents were asked which service they would not deploy an application without, they chose availability. Security came in a close second.
This caused a great deal of discussion. After all, one of the most often cited impediment to adopting, well, everything has been and remains security. One would think, then, that security is top of mind and clearly a priority for everyone.
Yet availability beat it out for what amounts to the "most important application service."
Back in 2003 I wrote an article that described the forthcoming evolution of the Cloud, and with it the development towards the SIngularity. The growing use of XML Web services would see them evolve to become intelligent agents, forming the basis for this collective.
This would fit well with the vision of the ‘Internet of Things’, where lots and lots of devices of all shapes and sizes will be equipped with an IP address and some small amount of self intelligence. Cars and traffic lights that are able to interoperate to better manage themselves for example.
Thanks to Docker, it becomes very easy to leverage containers to build, ship, and run any Linux application on any kind of infrastructure. Docker is particularly helpful for microservice architectures because their successful implementation relies on a fast, efficient deployment mechanism – which is precisely one of the features of Docker.
Microservice architectures are therefore becoming more popular, and are increasingly seen as an interesting option even for smaller projects, instead of being reserved to the largest, most complex application stacks.
Microservices, for the uninitiated, are essentially the decomposition of applications into multiple services. This decomposition is often based on functional lines, with related functions being grouped together into a service. While this may sound a like SOA, it really isn't, especially given that SOA was an object-centered methodology that focused on creating services around "nouns" like customer and product. Microservices, while certainly capable of being noun-based, are just as likely to be verb-based, that is to say, based on a functional grouping like "login" or "checkout." SOA was essentially an extension of object-oriented design while microservices are more about decomposition for purposes of rapid (agile) development with the bonus of having significant scalability advantages over object-oriented architectures.
It didn’t hit me until after a second viewing of Jez Humble’s recent webinar with Perforce that his ways to predict high IT performance aren’t just a neat party trick; they’re absolutely essential. The days of bugs making it into production, distrust between departments, and delayed fixes and releases are becoming a thing of the past, at least among “high performers” of the world.
And as the complexity of software grows year after year, being able to accurately predict success may be the only way to actually achieve it.
For three days and nights the Java master did not emerge from his cubicle. On the fourth day the monks of the temple sent a novice to inquire after him.
The novice found the master at his whiteboard, contemplating a single dataflow diagram. The novice recognized it as a minor component of the vast system that the monks were contracted to maintain. Politely, the novice asked what the master was...
Originally written by Stéphane Nicoll on the Spring blog
Application events are available since the very beginning of the Spring framework as a mean for loosely coupled components to exchange information. One of the most well known usage of application events is the following:
Application events are available since the...
HTML6 notion, despite the fact that the HTML5 specification was planned to fully adop
HTML6 notion, despite the fact that the HTML5 specification was planned to fully adopt and achieve the broadest possible compatibility in 2014, now began to appear ideas about how this specification of the next generation looks like –...
This post first started as I was discussing my post “You Aren’t Doing Scrum If …” with a friend who had read the post and was worried that I might not fit in an organization that wasn’t doing all of Scrum. I’ve since had other conversations and as I’ve reflected on the topic, I still stand by my original post, because there are some fundamental properties of Scrum that you...
Mobile by Rob LauerWhen you develop an Android app, your users will justifiably be concerned if your app requests access to a myriad of device features and personal information. You are risking decreased app installations and increased suspicions of your app’s motives if you ask your users for personal data, contacts, access to their phone, SMS messages, and so on. In this article I hope to...
you’ve been studying complex systems you know what minor changes might
cause consequences of much greater proportions, sometimes causing some
effects that are not easily explained at first. I recently ran across a
great illustration of such behavior while doing MySQL benchmarks which I
thought would be interesting to share.I’m using a very simple benchmark – Sysbench 0.5 on Percona...
Originally Written by Justin Swanhart
The JSON functions work very well for manipulating individual JSON objects, but like all other functions, using JSON_EXTRACT in the WHERE clause will result in a full table scan. This means the functions are virtually useless for searching through large volumes of JSON data...
In a previous blog post, I described using XmlNodePrinter to present XML parsed with XmlParser in a nice format to standard output, as a Java String, and in a
This post looks at how groovy.xml.XmlUtil can be used to present GPathResult objects that results from slurping XML to standard output, as a Java...
Hey, can you drop by and take a look at something weird”. This is how I started to look into a support case leading me towards this blog post. The particular problem at hand was related to different tools reporting different numbers about the available memory.
Hey, can you drop by and take a look at something weird”. This is...
Akin’s eighth law of spacecraft design says
In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.
When I first read this I immediately thought of several examples where theory said that an optima was at an extreme, but experience said otherwise.
Sometimes it’s rational to walk away from something you’ve invested a great deal in.
It’s hard to imagine how investors could abandon something as large and expensive as a shopping mall. And yet it must have been a sensible decision. If anyone disagreed, they could buy the abandoned mall on the belief that they could make a profit.
I came across a git repo recently that output this message with every operation I did:
Your branch is based on 'origin/master', but the upstream is gone.
(use "git branch --unset-upstream" to fixup)
I was delivering a workshop at the time so I kinda snarled at it and carried on with what I was doing, but later I looked up what is happening. This occurs when a branch is tracking a branch...
A few weeks ago we introduced the ByteSized DevOps Podcast series. Initial feedback from the community was very strong, so we've decided to do some more. We plan to release a few every week or two. Let us know what topics you'd like to see covered.
Monitoring and Logging
A few weeks ago we introduced the ByteSized DevOps...
Facets are annoying. Mostly because they tend to be used relatively rarely, but when they are used, they are used a lot, and in many interesting ways. Because they are fairly rarely used, let me explain what they are first.
We want to show the users all the recent phones. We can do this using the following query:
It often happens that a new piece of functionality is discussed within a team and different developers have a different preference over how it should be implemented. “But what if in the future…” is a typical argument, as well as “that way it’s going to be more extensible”.
It often happens that a new piece of...