Balhau

“Two different pieces of technology, Swagger and HAL, try to make this a reality, and both are worth looking at.”
― Sam Newman, Building Microservices: Designing Fine-Grained Systems

“Be careful about caching in too many places! The more caches between you and the source of fresh data, the more stale the data can be, and the harder it can be to determine the freshness of the data that a client eventually sees. This can be especially problematic with a microservice architecture where you have multiple services involved in a call chain. Again, the more caching you have, the harder it will be to assess the freshness of any piece of data. So if you think a cache is a good idea, keep it simple, stick to one, and think carefully before adding more!”
― Sam Newman, Building Microservices: Designing Fine-Grained Systems

“You’ll often see posts about people beating the CAP theorem. They haven’t. What they have done is create a system where some capabilities are CP, and some are AP. The mathematical proof behind the CAP theorem holds. Despite many attempts at school, I’ve learned that you don’t beat math.”
― Sam Newman, Building Microservices: Designing Fine-Grained Systems

“Zookeeper itself is fairly generic in what it offers, which is why it is used for so many use cases. You can think of it just as a replicated tree of information that you can be alerted about when it changes. This means that you’ll typically build things on top of it to suit your particular use case. Luckily, client libraries exist for most languages out there.”
― Sam Newman, Building Microservices: Designing Fine-Grained Systems