SKU: 56349535263

St. Theodosius the Great the Cenobiarch icon (2)

Sale price$18.00 Regular price$20.00
Save 10%

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 12 - Jul 17

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

St. Theodosius the Great the Cenobiarch icon (2)Orthodox icon of Saint Theodosius, Theodosios the Great, the Cenobiarch (2). Copy of an icon of 17 cent,, Monastery of Dionysiou, Mount Athos Commemorated January 11. Saint Theodosius the Great lived during the fifth sixth centuries, and was the founder of cenobitic monasticism. He was born in Cappadocia of pious parents. Endowed with a splendid voice, he zealously toiled at church reading and singing. St Theodosius prayed fervently that the Lord

Orthodox icon of Saint Theodosius, Theodosios the Great, the Cenobiarch (2). Copy of an icon of 17 cent,, Monastery of Dionysiou, Mount Athos

Commemorated January 11.

Saint Theodosius the Great lived during the fifth-sixth centuries, and was the founder of cenobitic monasticism. He was born in Cappadocia of pious parents. Endowed with a splendid voice, he zealously toiled at church reading and singing. St Theodosius prayed fervently that the Lord would guide him on the way to salvation. In his early years he visited the Holy Land and met with St Simeon the Stylite (September 1), who blessed him and predicted future pastoral service for him.  

Yearning for the solitary life, Saint Theodosius settled in Palestine into a desolate cave, in which, according to Tradition, the three Magi had spent the night, having come to worship the Savior after His Nativity. He lived there for thirty years in great abstinence and unceasing prayer. People flocked to the ascetic, wishing to live under his guidance. When the cave could no longer hold all the monks, St Theodosius prayed that the Lord Himself would indicate a place for the monks. Taking a censer with cold charcoal and incense, the monk started walking into the desert. At a certain spot the charcoal ignited by itself and the incense smoke began to rise.

Here the monk established the first cenobitic monastery, or Lavra (meaning broad or populous . Soon the Lavra of St Theodosius became renowned, and up to 700 monks gathered at it. According to the final testament of St Theodosius, the Lavra rendered service to neighbor, giving aid to the poor and providing shelter for wanderers. St Theodosius was extremely compassionate.

Once, when there was a famine in Palestine and a multitude of people gathered at the monastery, the monk gave orders to allow everyone into the monastery enclosure. His disciples were annoyed, knowing that the monastery did not have the means to feed all those who had come. But when they went into the bakery, they saw that through the prayers of the abba, it was filled with bread. This miracle was repeated every time St Theodosius wanted to help the destitute.

At the monastery, St Theodosius built a home for taking in strangers, separate infirmaries for monks and laymen, and also a shelter for the dying. Seeing that people from various lands gathered at the Lavra, the saint arranged for services in the various languages: Greek, Georgian and Armenian. All gathered to receive the Holy Mysteries in the large church, where divine services were chanted in Greek. During the reign of the Byzantine Emperor Anastasius (491-518) there arose the heresy of Eutychius and Severus, which recognized neither the sacraments nor the clergy.

The emperor accepted the false teaching, and the Orthodox began to suffer persecution. St Theodosius stood firmly in defense of Orthodoxy and wrote a letter to the emperor on behalf of the monks, in which they denounced him and refuted the heresy with the teachings of the Ecumenical Councils. He affirmed moreover, that the desert-dwellers and monks would firmly support the Orthodox teaching. The emperor showed restraint for a short while, but then he renewed his persecution of the Orthodox.

The holy Elder then showed great zeal for the truth. Leaving the monastery, he came to Jerusalem and in the church, he stood at the high place and cried out for all to hear: Whoever does not honor the four Ecumenical Councils, let him be anathema! For this bold deed the monk was sent to prison, but soon returned after the death of the emperor. St Theodosius accomplished many healings and other miracles during his life, coming to the aid of the needy.

Through his prayers he once destroyed the locusts devastating the fields in Palestine. Also by his intercession, soldiers were saved from death, and he also saved those perishing in shipwrecks and those lost in the desert. Once, the saint gave orders to strike the semandron (a piece of wood hit with a mallet), so that the brethren would gather at prayer. He told them, The wrath of God draws near the East. After several days it became known that a strong earthquake had destroyed the city of Antioch at the very hour when the saint had summoned the brethren to prayer.

Before his death, St Theodosius summoned to him three beloved bishops and revealed to them that he would soon depart to the Lord. After three days, he died at the age of 105. The saint's body was buried with reverence in the cave in which he lived at the beginning of his ascetic deeds.

Reference: O.C.A.

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: 56349535263

Discover Niche Categories That Outsell

Top-Converting Item to Boost Your Average Order

4.9 ★★★★★
Based on 207 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
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
Massapequa, 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
New York, 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
Houston, 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
M
M. Klocker
Fort Morgan, US
★★★★★ 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

recommand products