At its core DevOps is all about collaboration. The lines of communication
must be opened and it takes some effort to ensure that they stay that way.
It's easy to pay lip service to trends and talk about implementing new
methodologies, but without action, real benefits cannot be realized. Success
requires planning, advocates empowered to effect change, and, of course, the
To bring about a cultural shift it's important to share challenges. In simple
terms, ensuring that everyone knows what everyone else is doing can create a
real team spirit and social cohesion that will drive DevOps forward. Here are
six tips that can be implemented to help you get there.
A daily team meeting where people get an opportunity to review their progress
by addressing three simple questions:
What did I do yesterday? What will I do today? What might block me fro... (more)
DevOps is speeding towards the IT world like a freight train and the hype
around it is deafening. There is no reason to be afraid of this change as it
is the natural reaction to the agile movement that revolutionized development
just a few years ago. By definition, DevOps is the natural alignment of IT
performance to business profitability. The relevance of this has yet to be
quantified but it has been suggested that the route to the CEO's chair will
come from the IT leaders that successfully make the transition to a DevOps
model. If this still seems foreign to you, I recommend r... (more)
JANUARY 8, 2014 02:00 PM EST
When we talk about the impact of BYOD and BYOA and the Internet of Things, we
often focus on the impact on data center architectures. That's because there
will be an increasing need for authentication, for access control, for
security, for application delivery as the number of potential endpoints
(clients, devices, things) increases. That means scale in the data center.
What we gloss over, what we skip, is that before any of these "things" ever
makes a request to access an application it had to execute a DNS query.
Every. Single. Thing.
Maybe that's ... (more)
This is a no-hype, pragmatic post about why I think you should consider
architecting your next project the way SOA and/or microservices suggest. No
matter if it’s a greenfield approach or if you’re in dire need of
refactoring. Please note: considering still keeps open the option of not
taking that approach. After reading this, you will have a better idea about
whether building multiple small components instead of a single, large
component makes sense for your project.
This post assumes that you have experience with software architecture and
services (you’ll find some words about... (more)
I am not happy to Revisit a Vendor Survival post saying that my prediction
that a vendor will not survive was correct (for example, SUN).
If a vendor is not a monopoly, I am not happy to find that the probability
that it will survive is lower than it was (Apple, HP etc.).
Even if it is a monopoly in specific markets and not a monopoly in others, I
am not happy to find that its Survival probability is lower than it was
The reason that I am not happy is that competition is good for my customers:
They can buy better products and pay less.
This post is out of the ordinary. ... (more)
Red Hat is looking for a new name for the open source JBoss Application
Server, a k a JBossAS, because the JBoss Enterprise Application Platform has
gotten bigger than just Java.
So it's staging a community election to rechristen the widgetry with a name
that reflects polyglot programming and support for Java EE-alternative
frameworks like Spring.
In a press release issued Monday Red Hat said it is "embracing the evolution
of transformational technologies such as dynamic service fabric, cloud,
NoSQL, mobile and multi-language polyglot computing as part of its product
strategy. ... (more)