The white paper "Microservices for Java Developers (By O'Reilly) - Download Now" is no longer available on Infoq.com; However we invite you to explore the related content below.
Additional content from our sponsors:
-
Lyft’s Move to Microservices: A Case Study
It’s a challenge to quickly and accurately monitor Lyft’s system as the number of microservices grows, because a distributed architecture generates exponentially more data than its monolithic predecessor. To address this challenge, Lyft chose to implement [x]PM. Learn why.
-
Redgate's 2019 State of Database DevOps Report
Read the new Report for the latest insights into DevOps adoption among SQL Server professionals.
-
Manual Monitoring Bad! Automatic Monitoring Good!
In the race to keep software delivery up to pace with user expectations, manual monitoring puts all that at risk. The more your applications change, the more you must automate.
-
GSQL: An SQL-Inspired Graph Query Language
In this paper we compare GSQL to other prominent graph query languages in use today - Cypher and Gremlin. The comparison seeks to transcend the particular syntax or the particular way in which semantics are defined, focusing on expressive power classified along key dimensions.
-
The Only Good Reason to Adopt Microservices
Using microservices is absolutely the right way to scale your engineering organization because you‘re going to ship your org chart, no matter what. Learn More.
-
Microservices vs Service-Oriented Architecture (SOA) [Free O'Reilly Ebook]
So, what sets them apart? Are microservices really just “SOA done right”? How do the two approaches differ? More importantly, are microservices really better than SOA, or are we doomed to repeat the same mistakes of the past?
