Pay in installments of $95.38 with
,
and
Shipping Estimate
USA
- USA
- CAN
- USA
- CAN
Ships within 48 hours · Estimated delivery Aug 9 - Aug 14
Promo Codes Available:
For Your Every Summer RSVP, with Code: SUMMER15
Description
Honda VTX C / R / S 1800 & 1300 Bagger Fairing 6 x 9 Holes Batwing With StereoHeadlight Fairing for the Honda VTX C R S 1800 & 1300 Bagger Fairing Fiberglass 6 x 9 Holes Stereo Radio & Dual 6 x 9 speakers included Headlight Fairing for the Honda VTX C R S 1800 & 1300 Bagger Fairing Fiberglass 6 x 9 Holes Stereo Radio & Dual 6 x 9 speakers included This is a 100% fiberglass unit made here in the USA. This is not a cheap Chinese imitation unit, these are the thick, heavy duty units made by us and that will survive through the
Headlight Fairing for the Honda VTX C / R / S 1800 & 1300 Bagger Fairing - Fiberglass - 6 x 9 Holes - Stereo Radio & Dual 6 x 9 speakers included Headlight Fairing for the Honda VTX C / R / S 1800 & 1300 Bagger Fairing - Fiberglass - 6 x 9 Holes - Stereo Radio & Dual 6 x 9 speakers included This is a 100% fiberglass unit made here in the USA. This is not a cheap Chinese imitation unit, these are the thick, heavy duty units made by us and that will survive through the worst of the weathers ( now i would not recommend putting it through a tornado or hurricane) and thousands of miles later on your Harley. Get the good stuff here, made by Americans for Americans, we are riders who love our Harleys, we know the best and only want the best, so should you. Features: * Keep those ears humming and scare off those bad drivers with some good loud tunes while you are riding - great for people who can't see you but can now hear you = White head repellant. * Great wind deflection, keep the bugs on the fairing not on your face, better than most consumer bug sprays. * Unit is black primer coated - can be installed as is or painted. looks great either way, give your bike that extra custom look that others can't afford. * Manufactured with hand laid fiberglass by real fiberglass workers, I promise these guys take pride in their work not like some sweat shop workers. Stronger than that low cost Chinese plastic stuff. COMPLETE KIT INCLUDES: * FAIRING WITH DUAL 6 X 9 HOLES - WITH SPEAKERS AND RADIO INCLUDED. * 6 O-RINGES * NUTS AND BOLTS TO PUT THE FAIRING TOGETHER. * RADIO/CD PLAYER WITH IPOD HOOKUP (XM/SIRIUS READY) * BUILT IN ANTENNA * DUAL 6 X 9 MARINE WATERPROOF SPEAKERS Clamps to fork tubes between the triple trees; will not work with Spec 2 or 3-type chrome fork tube covers NOTE: PLEASE SEE A PROFESSIONAL FOR INSTALLATION The 1800 fairing can fit on the Honda VTX 1300 Honda VTX 1300 R & S models: The R & S model fork tubes between the triple trees are covered with sheet metal shrouds that have to be removed for the fairing installation. This entails you to remove the top tree to slide the shrouds off the tubes, which should be done according to your shop manual. After you have removed the shrouds, the fairing can be installed on the bare fork tubes with the use of PVC pipe spacers. The spacers are needed because the inverted forks on the 1800 model (which the fairing is a custom fit to) are a larger diameter than the 1300 model. Without the spacers the mounting clamps would crush the fiberglass fairing. Honda VTX 1300 C model: The C model fork tubes needs only the spacers to physically mate up the fairing, but there is a interference problem with the turn signals. They have to be removed from the fork tubes to allow the fairing to be mounted. If relocated below the lower tree they may interfere with the front suspension travel, so we don't recommend that. Custom turn signals are suggested *** BIKE MUST BE EQUIPED WITH HARDWARE TO ACCEPT NORMAL WINDSHIELD IN ORDER TO ACCEPT THIS FAIRING. WE ONLY PROVIDE THE HARDWARES TO ATTACH THIS FAIRING TO YOUR ORGINAL HARDWARE. About Bagger Bags: Bagger Bags specializes in custom Harley Davidson accessories and replacement parts. We offer Harley aftermarket parts that are not only unique but of great quality.All of our HD parts are made by hand with extreme detail, we only use real fiberglass sheets and 100% grade A carbon fiber materials to make our Harley Davidson products. All of our HD custom products are handmade and hand laid with a minimum of 3 layers of fiberglass, so that you know you are getting a thick quality product that is easy to repair in case of a mishap. Abs is not as sturdy as fiberglass and ABS products unfortunately do not give you the ability to do repairs in case of a hard shock or accident in most cases, your product will be more prone to breaking in several pieces rendering it impossible to repair whereas fiberglass does.Shipping Notes
- Free Standard Shipping on $100+ Orders to the USA.
- Except Preorder products are shipped in 48 hours.
- Delivery to the USA:
- Standard Shipping : 3-10 business days
- If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
- We offer a 30-day return/exchange service after receiving.
- Final sale items are not eligible for returns or exchanges.
- To process your return/exchange, please contact us at [email protected]
- Please click here for more details>>> Return & Exchange Policy
4.2 ★★★★★
Based on 24 reviews
Sort
Product Reviews
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend.
I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this.
Let's summarize some key insights -
-- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud.
-- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services.
-- Distinguish between "availability" and "uptime" and measure each separately, and concretely.
-- In FaaS/Serverless, calling a function synchronously increases debugging complexity.
-- Good code is like good joke - it needs no explanation.
-- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains.
-- Cloud is not optimized for replacing static infrastructures.
-- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra.
-- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less.
-- Adopt an "assume breach" stance for everything. Have a break-glass account.
-- Ensure you have a thorough understanding of where and how secrets are secured.
-- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop.
-- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure.
-- Resilience is something you "do", not something you "have". Resilience is a verb.
-- Moving from one class of nines to the next is 10 times more expensive.
-- Production System really means "system that someone else, anyone else, can hold you accountable for".
-- Most common theme across incidents is that something, somewhere was surprising.
-- Incidents are unplanned investments...your challenge is to maximize ROI.
-- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases).
-- Architecture diagram is also a map of failure modes.
-- Async communication is a friend of Cloud Reliability.
-- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env.
-- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign.
-- It is hard to write good tests for bad code.
-- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023
★★★★★ 2
Shallow, biased and significantly overpriced
Format: Paperback
Well, this purchase was a disappointment. 20% of the pages are dedicated to just highlighting the bios and backgrounds of the many different authors that contributed this great wisdom. And let me be clear, the authors are solid. They are professionals with credible backgrounds and experience. But it's the format and constraints of this book that makes it virtually impossible for that to shine through. Because the rest of the book (80%) is dedicated to the so called "97 things every cloud engineer should know". And unfortunately the average length of one of these "things" is about 1.5 pages long, and as such extremely shallow and in about 30% of the cases straight up promotions for specific company services. You will find Google cloud advocates telling you to use managed services, of Google of course. AWS engineers telling you to avoid them and use IaaS. LaunchDarkly employees telling you to use feature flags. The list goes on. The TL;DR: here is that if you have built anything on the cloud in the last 2 years, this book is going to be a waste of your time and money. You are better of googling: "cloud best practices" and dedicating 2h to reading the first 10 non-ad related search results.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on March 23, 2022