SKU: 78192503596

Pio Cesare - Barolo Ornato

Sale price$112.49 Regular price$124.99
Save 10%

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 10 - Jul 15

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

Pio Cesare - Barolo OrnatoPio Cesare Barolo Ornato 2020 Barolo DOCG Pio Cesare Barolo Ornato 2020 is de single vineyard Barolo van dit historische huis in Alba, afkomstig van de cru Cascina Ornato in Serralunga dAlba. Ornato is het krachtige, gespierde gezicht van Pio Cesare, met oude Nebbiolo stokken op een amfitheatervormige, volledig zuidgerichte helling. Is Pio Cesare Barolo Ornato 2020 een wijn om lang te bewaren? Wijngaarden en regio De druiven voor Barolo Ornato 2020

Pio Cesare Barolo Ornato 2020 Barolo DOCG

Pio Cesare Barolo Ornato 2020 is de single vineyard Barolo van dit historische huis in Alba, afkomstig van de cru Cascina Ornato in Serralunga d’Alba. Ornato is het krachtige, gespierde gezicht van Pio Cesare, met oude Nebbiolo-stokken op een amfitheatervormige, volledig zuidgerichte helling. Is Pio Cesare Barolo Ornato 2020 een wijn om lang te bewaren? 

Wijngaarden en regio

De druiven voor Barolo Ornato 2020 komen uit Italië, uit Piemonte, uit de Barolo DOCG, uit de cru Cascina Ornato in Serralunga d’Alba. De wijngaard vormt een natuurlijke kom met volledige zuidexpositie, van de vroege ochtend tot de late namiddag, waardoor Nebbiolo hier optimaal kan rijpen zonder zijn frisheid te verliezen. De bodem bestaat uit kalkrijke mergel en klei met zandige insluitsels, typisch voor Serralunga d’Alba, wat zich vertaalt in krachtige tannines, veel structuur en een duidelijke minerale ondertoon in de wijn.

Ornato was een van de eerste grote wijngaardaankopen van de familie Pio in Serralunga d’Alba en geldt binnen Pio Cesare als een van de toppercelen van het domein. Alleen de beste microplots in de cru worden geselecteerd voor Barolo Ornato en de opbrengsten worden bewust laag gehouden om de intensiteit van fruit en terroir te maximaliseren. Het familiehuis zelf staat nog altijd binnen de oude Romeinse stadsmuur van Alba, waar inmiddels vijf generaties Pio Cesare een klassiek georiënteerde maar precies uitgevoerde stijl hebben opgebouwd.

Vinificatie en rijping

De oogst voor Barolo Ornato 2020 gebeurt volledig met de hand, met strenge selectie van de trossen in de wijngaard en bij aankomst in de kelder. De druiven worden ontsteeld en vergisten in roestvrijstalen tanks bij relatief hoge temperatuur, met een lange schilmaceratie van ongeveer 30 dagen, zodat kleur, aroma en tannines stap voor stap uit de schillen worden gehaald. Deze klassieke Barolo-vinificatie levert een stevige structuur op, maar dankzij de precieze temperatuurcontrole blijven de aroma’s helder en verfijnd.

Na de vergisting rijpt het grootste deel van de wijn ongeveer 24 maanden in grote eikenhouten vaten van Frans en Oost-Europees eiken. Een kleiner deel van de wijn rijpt parallel in Franse eiken barriques tijdens de eerste 12 maanden, wat extra gelaagdheid, zoete specerijen en een subtiele toasttoon geeft. Na het assembleren van de afzonderlijke partijen volgt nog een periode flesrijping in de kelders van Alba, totdat de structuur van de wijn voldoende is versmelt. Het resultaat is een Barolo met serieuze kracht en concentratie, maar met verfijnde tannines en een opvallend nauwkeurige, lineaire stijl, bedoeld voor lange bewaring.

Druivensamenstelling

Nebbiolo – Cascina Ornato, Serralunga d’Alba
Pio Cesare Barolo Ornato 2020 is 100% Nebbiolo uit geselecteerde microplots in de cru Ornato, waar de combinatie van kalkrijke mergel, volle zuidexpositie en lage opbrengsten zorgt voor intens rood fruit, krachtige maar rijpe tannines en een uitgesproken mineraal karakter.

Proefnotities en serveertips

In het glas toont Barolo Ornato 2020 een robijnrode kleur met granaatkleurige reflecties. De neus is complex en gelaagd, met aroma’s van kers en rode bes, rijpe aardbei en cranberry, gecombineerd met tonen van rozenblaadjes, viooltjes, witte peper, zoete specerijen, cacao en een vleugje grafiet en rook. Bij het walsen komen meer balsamische nuances naar voren, met hints van menthol, kruidigheid en iets van gedroogde sinaasappelschil.

De smaak is vol en geconcentreerd, met een kern van puur rood en donker fruit, strak geweven, rijpe tannines en een levendige, bijna “snappy” zuurgraad die de wijn lengte en spanning geeft. De textuur is krachtig maar gepolijst, met een lange afdronk waarin fruit, specerijen, minerale tonen en subtiele houtaroma’s lang blijven doorlopen. Serveer Barolo Ornato 2020 idealiter rond 16–18 °C in een ruim glas en geef de wijn royaal lucht, zeker in zijn jeugd, bijvoorbeeld 3 tot 4 uur in de karaf. Aan tafel past hij uitstekend bij langzaam gegaard rundvlees, stoofgerechten van wild, lamsrack, rijke paddenstoelengerechten met truffel en bij gerijpte harde kazen, waar zijn kracht, frisheid en complexiteit volledig kunnen schitteren.

Bekroningen

  • 2020 – 98 p (James Suckling)
  • 2020 – 95 p (Robert Parker’s Wine Advocate)
  • 2020 – 97 p (Decanter)
Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. 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
SKU: 78192503596

Discover Niche Categories That Outsell

Top-Converting Item to Boost Your Average Order

4.3 ★★★★★
Based on 1899 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
A
Amazon Customer
Pawtucket, US
★★★★★ 5
This is a "Go-To" for thinking about Cloud Challenges.
Format: Paperback
Delivering and managing fully realized applications in the cloud is different. Different approaches to classic engineering problems than traditional On Premise development and different ways of thinking through the problems of "always available" solutions. I've been in the software delivery business a long time, and with the cloud emerging, for good and ill: I understand the problems, but may be just a little set in my ways. I find this book helps me re-frame challenges in a way that aligns with the strengths of cloud computing. Solve the same problems faster, by thinking about them differently. I'm finding "97 Things Every Cloud Engineer Should Know" great for re-centering my expectations about Cloud Native development and deployment of assets. I started reading it cover to cover over the Christmas Holiday but now i just pick it up and look for the group of essays about exactly the problem I'm wrestling with. P.S. I'm heartened by the editors commitment to Black Lives Matter and Rule of Law. Mentioned only to balance the concerns from another review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on January 24, 2021
C
Verified Purchase
cloud-learner
Lowell, US
★★★★★ 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
E
Verified Purchase
Engineer Dude
Pawtucket, US
★★★★★ 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
P
Verified Purchase
PeaceBee
Houston, US
★★★★★ 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
N
Nilendu Misra
New York, US
★★★★★ 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

recommand products