Topics

Featured in Development

As part of our core values of sharing knowledge, the InfoQ editors were keen to capture and share our book and article recommendations for 2018, so that others can benefit from this too. In this second part we are sharing the final batch of recommendations

Featured in Architecture & Design

Tanya Reilly discusses her research into how the fire code evolved in New York and draws on some of the parallels she sees in software. Along the way, she discusses what it means to be an SRE, what effective aspects of the role might look like, and her opinions on what we as an industry should be doing to prevent disasters.

Featured in Culture & Methods

Mik Kersten has published a book, Project to Product, in which he describes a framework for delivering products in the age of software. Drawing on research and experience with many organisations across a wide range of industries, he presents the Flow Framework™ as a way for organisations to adapt their product delivery to the speed of the market.

Featured in DevOps

The fact that machine learning development focuses on hyperparameter tuning and data pipelines does not mean that we need to reinvent the wheel or look for a completely new way. According to Thiago de Faria, DevOps lays a strong foundation: culture change to support experimentation, continuous evaluation, sharing, abstraction layers, observability, and working in products and services.

The InfoQ eMag: Microservices - Patterns and Practices

About the Author

InfoQ.com is facilitating the spread of knowledge and innovation in professional software development. InfoQ content is currently published in English, Chinese, Japanese and Brazilian Portuguese. With a readership base of over 1,400,000 unique visitors per month reading content from 100 locally-based editors across the globe, we continue to build localized communities.

The InfoQ Newsletter

A round-up of last week’s content on InfoQ sent out every Tuesday. Join a community of over 250,000 senior developers.
View an example

While the underlying technology and patterns are certainly interesting, microservices have always been about helping development teams be more productive. Whether used as a technique for architects to manage complexity or to make small teams more independent and responsible for supporting the software they create, the human aspect of microservices cannot be ignored.

Many of the experts who spoke about microservices patterns and practices at QCon San Francisco 2017 did not simply talk about the technical details of microservices. They included a focus on the business side and more human-oriented aspects of developing distributed software systems.

Free download

Microservices: Patterns and Practices eMag includes:

Polyglot Persistence Powering Microservices - At Netflix, the cloud database engineering team is responsible for providing several flavors of data persistence as a service to microservice development teams. Roopa Tangirala explained how her team has created self-service tools that help developers easily implement the appropriate data store for each project's needs.

Patterns for Microservice Developer Workflows and Deployment: Q&A with Rafael Schloming - Drawing on his experience with developing a microservices application at Datawire in 2013, Rafael Schloming argued that one of the most important — although often ignored — questions a development lead should ask is "How do I break up my monolithic process?" as the development process is critical to establishing and maintaining velocity.

Debugging Distributed Systems: Idit Levine Discusses the Squash Microservices Debugger - With microservices distributed across containers, how is a developer able to step into the code and debug what is happening? Idit Levine discussed the problem and introduced Squash, an open-source platform for debugging microservices applications.

Microservices Patterns and Practices Panel - In this panel discussion several experts shared their experiences and advice for being successful with microservices. Questions from the audience highlighted common themes, such as dealing with deployments, communication between microservices, and looking at what future trends might follow microservices.

Managing Data in Microservices - Randy Shoup provided practical examples of how to manage data in microservices, with an emphasis on migrating from a monolithic database. He also strongly advocated for building a monolith first, and only migrating to microservices after you actually require the scaling and other benefits they provide.