Book Notes

Chapter 11 Main Takeaways: Britain initially supported Ethiopia's claim to Eritrea because it wanted the Ogaden France was opposed to Ethiopia gaining access to port.  Pakistan, Guatemala, Burma, South Africa, and Norway were picked to inquiry the wishes of the population of Eritrea as to the fate of their land.  United States initially opposed Ethiopian trusteeship over Eritrea  The Muslim nations were opposed to Ethiopian trusteeship over Eritrea  Italy was main opponent to Ethiopia's claim on Eritrea Zeila: Ethiopia entertained the idea of claiming a portion of Somalia, specifically to gain access to a sea port via Zeila this idea was entertained by Britan but fell through because France opposed it Italy: Promoted Eritrea gain independence, with the idea that it will be able to retain its influence Italy promoted the independence movement in Eritrea by providing financial support (213) Interesting facts: Emperor Menelik was the fifth husband for the Empress Taitu ...

Title: Designing Data-Intensive Applications Author: Martin Kleppmann Publication date: March 2017 Print length: 616 pages Chapter 1 Thinking About Data Systems There are datastores that are also used as message queues (Redis), and there are message queues with database-like durability guarantees (Apache Kafka). The boundaries between the databases, queues, caches, etc. are becoming blurred Increasingly many applications now have such demanding requirements that a single tool can no longer meet all of its data processing and storage needs. Instead, the work is broken down into tasks that can be performed efficiently on a single tool, and those different tools are stitched together using application code. If you are designing a data system or service, a lot of tricky questions arise. How do you ensure that the data remains correct and complete, even when things go wrong internally? How do you provide consistently good performance to clients, even when parts of your system are degrad...

Title: Building Microservices, 2nd Edition Author: Sam Newman Publication date: August 2021 Print length: 612 pages Chapter 1 Microservices are a type of service-oriented architecture.  Deployability is key for a microservices. to ensure independent deployability, we need to make sure our microservices are loosely coupled Having clear, stable service boundaries that don’t change when the internal implementation changes results in systems that have looser coupling and stronger cohesion. Model services around business domains it will make it easier to roll out new functionality and to recombine microservices in different ways to deliver new functionality microservices should be slices of business functionality that encapsulate user interface (UI), business logic, and data Microservices should avoid the use of shared databases if a microservice wants to access data held by another microservice, it should go and ask that second microservice for the data Microservice should be kept...