Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Containers Expo Blog

Containers Expo Blog: Blog Post

Three Things You Didn't Know About BIG-IP

Some of the things you didn't really know about BIG-IP

There's a lot of things people know about F5 BIG-IP and a lot of things people think they know about BIG-IP and some things people don't know at all about BIG-IP*.

So I thought it'd be a good idea to talk about some of the things you don't know about BIG-IP or in some cases, the things you didn't really know about BIG-IP. Kind of a myth-busting post, if you will.

So without further ado, let's get onto the list, shall we? It's Friday, after all, and there's an Internet full of cat videos waiting to be watched.

1. BIG-IP is not hardware. hardware-vs-software-big-ip

Oh, I know, F5 delivers BIG-IP on hardware that's called BIG-IP XXXX so really, what's the difference?

BIG-IP is a product family, a brand if you will. It's a way to identify that "these products are related" and go together. We could call it just the XXX hardware platform, but because it's specifically designed to enhance BIG-IP software, it kind of makes sense to group them together under the same name. I mean, it's not like you're going to deploy anything other than BIG-IP software on BIG-IP hardware, right?

But you might (and probably will) deploy BIG-IP software in a virtual form factor (we support all major hypervisors - Citrix, VMware, KVM, Microsoft) - or in a cloud like AWS, Rackspace, Microsoft Azure or VMware vCloud Air. That's because the BIG-IP software is not reliant on BIG-IP hardware. Oh, it benefits from BIG-IP hardware because the hardware is designed to enhance the performance and scale of the BIG-IP software but it's not a requirement. The BIG-IP software is enhanced by, not dependent on, BIG-IP hardware.

And software it is. With over 15 years of development, it's a significant piece of software. And most of that code is dedicated to TMOS and the modules from which our application services are ultimately delivered. Some of the code is specific to BIG-IP hardware, in order to eke out the most performance and scale out of the system, but that code is abstracted enough that the bulk of the software is deployable just about anywhere.

But that doesn't mean you have to pair the two together. You can certainly enjoy the benefits of BIG-IP software (which include the extensibility of any other software platform) without simultaneously employing the use of BIG-IP hardware.

2. BIG-IP is not just a load balancer.

I know, surprise right? Granted, BIG-IP is almost universally synonymous with load balancing because that's where we started and well, it's really uber awesome at load balancing. But that's just one service out of a large (and growing) number of services available for BIG-IP. That's because BIG-IP is not just software, it's a software platform. And platforms are meant to be extended. In the case of BIG-IP that's through software modules that deliver one or more application services. BIG-IP APM (Access Policy Manager), for example, offers not only SSL-VPN services but cloud identity federation services and application access control as well as identity services and protocol gateway services.

I will not deluge you with a complete list, but trust me that there are a plethora of services spanning device, network and application foci to choose from. And the list keeps growing. For example, just this past year we added secure web and HTTP/2 gateway services. Because it's a platform, not a product.

BIG-IP software is based on a full-proxy architecture, meaning its got a dual stack - one for the client-side and one for the app-side. That gives it tremendous flexibility in how it can interact with application traffic and data. Sure, it can load balance the heck out of your apps like nobodies business (and with more efficacy and intelligence than any other solution out there) but it can also do just about anything an app can do, too because the separation of the stacks means it is, technically, an app itself. It's an endpoint, just like your app server.

Now, you can't write just anything and deploy it on BIG-IP software because the platform is for us to use to develop new services. But you can write code that runs within the context of any service and interact with the platform to gather statistics, change behavior and call out to other services to share or gather information important to the app or the service itself.

That's a far sight more than just a "load balancer", isn't it?

3. BIG-IP delivers application services which are not the same as application networking services.

I know this might seem pedantic, but it's an important distinction that needs to be made sooner rather than later. I'm not going to diagram sentences to explain this one, but when we say "application services" we mean "services for applications." When you say "application networking services" you are saying "networking services for applications". There's a big difference there in what that ultimately means. Networking services are those that connect, transport, and secure network traffic. When they're focused on applications it means that those services are acting on behalf of applications.

When we say "application services" we're talking about intermediate services that reside in the data path and offer application-specific functionality. Web application security, for example, must (if it's going to have any degree of efficacy) be application-specific. It's not just about transporting traffic from point A to point B, it's about performing a service on behalf of the application that improves its security, availability or performance. They aren't "networking" in the traditional sense that networking is about routing and switching and firewalling. They are networking in that they operate at the upper layers (4-7) of the OSI network stack. But operationally they are targeted applications themselves (see #1 above) that just happen to be located "in" the network because it makes sense to topologically deploy those services upstream from the application.

After all, when the point of a service is to prevent bad requests from consuming resources unnecessarily or compromising an application it makes sense to ensure that process happens before the request actually gets to the application.

Yes, BIG-IP also provides some application networking services, like acting as a protocol transition point - from SPDY or HTTP/2 to HTTP/1 and vice versa or from IPv4 to IPv6 and its reverse or from VXLAN to VLAN to NVGRE or whatever combination of SDN overlay protocol you're looking to use. But the bulk of services delivered by a BIG-IP are application services. No additional modifier required.

There you have it. Three things you (perhaps | mostly | almost) didn't know about BIG-IP that now you do. And we all know that knowing is half the battle.

The other half is red and blue lasers.

Happy Friday!

* If that sounds sort of like Bilbo Baggin's farewell speech at his 111th birthday party then I did it right.

Read the original blog entry...

More Stories By Lori MacVittie

Lori MacVittie is responsible for education and evangelism of application services available across F5’s entire product suite. Her role includes authorship of technical materials and participation in a number of community-based forums and industry standards organizations, among other efforts. MacVittie has extensive programming experience as an application architect, as well as network and systems development and administration expertise. Prior to joining F5, MacVittie was an award-winning Senior Technology Editor at Network Computing Magazine, where she conducted product research and evaluation focused on integration with application and network architectures, and authored articles on a variety of topics aimed at IT professionals. Her most recent area of focus included SOA-related products and architectures. She holds a B.S. in Information and Computing Science from the University of Wisconsin at Green Bay, and an M.S. in Computer Science from Nova Southeastern University.

@MicroservicesExpo Stories
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...