To summarize: If you don’t get enough sleep you are destroying your mind and body.
I’ve been meaning to write about my recommended reading list for a while. Unexpectedly, the first book on my list is not a book about software development. Instead, it’s Why we sleep: Unlocking the Power of Sleep and Dreams by Mathew Walker, who is a professor of neuroscience and psychology at UC Berkeley, the Director of its Sleep and Neuroimaging Lab, and a former professor of psychiatry at Harvard University. I bought the book after reading an interview with the author in the Financial Times and couldn’t put it down.
In addition to the fascinating scientific explanation of sleeping and dreaming, there are numerous horrifying experimental findings including
Cognitive impairment (p. 136): “Ten days of six hours of sleep a night was all it took to become as impaired in performance as going without sleep for twenty-four hours straight.”
Athletic impairment (p. 129): “Obtain anything less than eight hours of sleep a night, and especially less than six hours a night, and the following happens: time to physical exhaustion drops by 10 to 30 percent, and aerobic output is significantly reduced.”
Reduced effectiveness of vaccinations (p. 183): “In contrast, those in the sleep-restricted group mustered a paltry response, producing less than 50 percent of the immune reaction their well-slept counterparts were able to mobilize.”
Alcohol inhibits REM sleep, which is vital for memory and creativity (p. 272): “Second, alcohol is one of the most powerful suppressors of REM sleep that we know of.”
Sleep deprived employees are bad for business (p. 300): “Under-slept employees are not, therefore, going to drive your business forward with productive innovation.”
Less sleep leads to poor health (p. 165): “Over a fourteen-year period, those sleeping six hours or less were 400 to 500 percent more likely to suffer one or more cardiac arrests than those sleeping more than six hours.””
This is just a small sample of the science that shows that sleep is the foundation of a long, healthy and creative life. Ironically, I’m writing this while jet lagged in Seoul, South Korea.
Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.
Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.
Chris teaches comprehensive workshops for architects and developers that will enable your organization use microservices effectively.
Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.Learn more
Chris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!
It covers the key distributed data management patterns including Saga, API Composition, and CQRS.
It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.
The regular price is $395/person but use coupon MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.
Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · loose coupling · microservice architecture · microservice chassis · microservices adoption · microservicesio updates · multi-architecture docker images · observability · pattern · refactoring to microservices · resilience · sagas · security · service api · service collaboration · service design · service discovery · service granularity · service template · software delivery metrics · success triangle · tacos · team topologies · transaction management · transactional messaging