Back in the day - when the Internets were exploding and I was still coding -
I worked in enterprise architecture. Enterprise architecture, for the record,
is generally not the same as application development. When an organization
grows beyond a certain point, it becomes necessary to start designing a
common framework upon which applications can be rapidly developed and
Architects design and implement this framework and application developers
then code their applications for deployment on that architecture.
If that sounds a lot like PaaS it should because deep down, it is.
The difference with PaaS is its focus on self-service and operationalization
of the platform through automation and orchestration. Traditional enterprise
architectures scaled through traditional mechanisms, while PaaS enables a far
more fluid and elastic model for scalability and a more se... (more)
#NodeSummit #devops #nodejs #F5 #LineRate
The last time F5 had a presence at a #devops conference (Glue) we heard the
same question multiple times. "What is F5 doing here?" It was a good
question, one we couldn't necessarily answer directly because, well, we
weren't ready to answer. But this time, when you ask "What is F5 doing at
Node Summit?" we're not only ready to answer that question, we're excited to
Node Summit is a relatively new gathering of business leaders and technology
experts coming together to discuss and present on the transformative role of
Node.js i... (more)
One of the "rules" of application delivery (and infrastructure in general)
has been that when scaling out such technologies, all components must be
equal. That started with basic redundancy (deploying two of everything to
avoid a single point of failure in the data path) and has remained true until
Today, fabrics can be comprised of heterogeneous components. Beefy, physical
hardware can be easily paired with virtualized or cloud-hosted components.
This is good news for organizations seeking the means to periodically scale
out infrastructure without oversubscribing the ... (more)
To achieve the economy of scale necessary to ensure no application is
deprived of critical application services, you need to abstract resources.
In the early days of cloud computing we talked a lot about how the economy of
scale offered by cloud was achieved mainly through abstraction of resources.
Compute, network and storage resources were abstracted and pooled together
such that they could be provisioned as services on-demand.
That economy of scale ensured that the cost of using those services
decreased, making them affordable for even the smallest of organizations.
In the data... (more)
The silos within IT are breaking down, at least in terms of awareness of each
other and the need to coordinate provisioning and orchestration of compute,
network and application services. No longer is it acceptable to simply
provide a solution; that solution must integrate, collaborate and
interoperate with a plethora of existing and emerging data center
technologies such as SDN, cloud management platforms, and virtualization
After all, part of the raison d'être for SDN is the need to enable the
network with the agility and flexibility of its counterparts- devops and... (more)