Still chugging along with a monolithic enterprise system that’s difficult to scale and maintain, and even harder to understand? In this concise report, Lightbend CTO Jonas Bonér explains why microservice-based architecture that consists of small, independent services is far more flexible than the traditional all-in-one systems that continue to dominate today’s enterprise landscape.
You’ll explore a microservice architecture, based on Reactive principles, for building an isolated service that’s scalable, resilient to failure, and combines with other services to form a cohesive whole. Specifically, you’ll learn how a Reactive microservice isolates everything (including failure), acts autonomously, does one thing well, owns state exclusively, embraces asynchronous message passing, and maintains mobility.
Bonér also demonstrates how Reactive microservices communicate and collaborate with other services to solve problems. Get a copy of this exclusive report and find out how to bring your enterprise system into the 21st century.
Jonas Bonér is Founder and CTO of Lightbend, inventor of the Akka project, co-author of the Reactive Manifesto and a Java Champion. Learn more at: http://jonasboner.com.
It's free, it's brief, it makes sense, it's a proper primer for an important topic that gets a lot of attention these days. But it's still just a primer, far from covering all important perspectives (e.g. deployment, configuration mgmt) - I'd rather suggest going for (commercial) "Building Microservices" by Sam Newman if you want a full picture.
This short book is recommended as source of "concepts" for Langom microservices frameworks. It introduces a lot of basic concepts, with links to other sources...
Golden Gate to Realistic Distributed Systems. The book is full of references to articles and proofs about distributed systems that will help a lot. I recommend it for every software developer that don't know much about distributed systems.
Free paper with dozens of links and brief explanation of ideas which you have to implement to properly manage microservices. Good starting point for such journey.
Ranked in regard to personal usefulness. If you're kind of "detached" from recent trends this might be a useful read as it gives a general overview of what microservices are about. Otherwise there will probably be nothing new to you.
What I liked about this book, though, are the references to external resources and papers - this is valuable.
Not actually a "book" per se, but more like a paper -- the author even mentions it is a paper.
Now, is it a good paper? Well... Thing is, easy-to-explain concepts, like "Sagas", take a long discussion about them, but hard-to-explain, like the CAP theorem, make just some short explanations. And this is bad; things that really need more explanation do not and are just glossed over; things that you can get right out of the bad, do not. Also, some parts put a lot of footnotes and assume the reader will read the footnote, which is bad, 'cause if you let it to read later, you won't totally grasp what it means.
Also, there is one serious problem: Although it does a good discussion about microservices, there is is very little explanation on what the reactive microservice differs from normal microservices.
It's more interesting for the footnotes, which have links to the real content, than the content of the paper.
A good, concise, overview of important concepts for designing robust APIs and microservices. This free ebook does not go into the details much (probably on purpose), but it does provide some high level, real world examples on what to consider when designing complex, distributed systems. As an engineer, I found it useful to familiarize myself with some industry jargon, to help me "talk the talk" when communicating my concerns and ideas with other engineers and directors. I also liked the quotes and metaphors used throughout the book, to draw parallels between software development and the real world.
Good for an introduction or summary on microservices. Every one has his/her own opinion about this topic -- this is another one.
I do not see such a big difference between reactive and "normal" microservices architecture. For me, a good architected microservices landscape has the properties mentioned in this flyer -- and I do not consider it reactive (although I have signed the rective manifesto too).
Small and concise book on Microservices. Not much, but all you need to remind or start digging deeper. Good intro. One thing I don't agree on the book: microservices are silver bullet and monoliths are pure evil. This is just not true and I was seeing lots of system struggling with microservices which they've added because it was on hype. And such books encourage that. That's probably bad, you need to always think and think a lot before making something
Nice summary book to summarize many concepts in the reactive microservices architecture world. References are also very good. Will not be useful to someone not familiar with these concepts but will be a good refresher to someone who is and at the same time you may find a reference you didn't know about.
Easy and light introduction to the very basics of microservice architecture ideas. The book is not intented to give you the full picture and deep dive into the topic, but only an overview. It does the job well, and I liked the quotes very much :).
It seems a bit chaotic, but introduces a lot of fundamental concepts that can be further explored (there's plenty of reference material mentioned in footnotes). Overall it is a good introductory booklet.
A small booklet about microservices would only recommend if you want an extremely brief summary of considerations to take when building microservices. However, if you really want to read about the topic, Sam Newman books are a much better option.
It's a really really short introduction to microservices, there is plenty of other materials with more content and better structure. But, it's free ad it's really short. So... Yeah, I can recommend it as a good starting point, but do not expect anything more than that.
Quite a good summary what is the reactive microservice architecture about. I was looking for information on saga pattern and that is overviewed well here with nice list of resources.
Way too small to really teach you how to implement all those concepts, but filled with lot of interesting pointers which makes it a quick, but really good read. And it's free.
This book is, at worst, a sale pitch for micro-services and its tool chain; at best, a collection of references which only provide fragmented knowledge. It doesn't provide much information for someone who try to understand or build a micro-services architecture.
This isn't my area at all—I don't do any web/network programming—but I keep peeking over the fence. I must find something interesting about this [now seemingly ubiquitous] aspect of the coding world. Full disclosure out of the way, this felt, to this non-expert, like a solid report from the trenches on the history and current state of microservices, authored by a veteran, stated clearly and succinctly—and conveniently—in 50 pages. Those who get the references should find some clarity, and a highlighting of any gaps in knowledge, with links to additional info to fill in the gaps. Those like me, whose knowledge is nothing but one giant gap, will find a few dozen links to more info spread evenly throughout the book, with the crux of each tied to the others, creating a sense of the whole, and of the work that would be required of a novice to to get comfortable and proficient. This novice really appreciated the illumination.
A short book to give you a quick start on the topic of microservices. With only 54 pages there is simply no place for details. But when you just want to know what microservices are all about and which problems they should solve, then this book is a good read for you.
This mini book serves very well as an introduction to microservices. It describes, compares and explains microservices with lot of references for further study. I would give it five stars for more details about the (non)reactive aspect.
This book is mostly a summary of things you may want to dig into while building Microservices oriented system. It lacks examples though and sometimes it just lists through concepts without really explaining why it's good to use them.
Great as an overview/introduction into the world of microservices and also fantastic as a collection of references - blog posts, articles, papers - but not much more than that. Nevertheless I enjoyed reading it and would recommend using it as a cheat-sheet or a reference book of sorts.
Nice overview of what helps to migrate to microservices and some initial pointers. Not really an in depth but just an introduction; hey it is 50+ pages long don't expect that much.