|
Welcome to the InfoQ Software Architects' Newsletter! Each month, we bring you essential news and experience from industry peers on emerging patterns and technologies.
This month, we focus on the topic of "Microservices: Past, Present, and Future". The topic of "microservices" is currently listed in the "late majority" category of adoption in our most recent Architecture and Design InfoQ Trends Report, but the topic of "correctly built distributed systems" is listed as only "early majority". Key challenges remain for architects designing such systems, including both human and technical issues.
News
What Have We Learned over the Last Decade of Microservices?
This InfoQ episode is a panel discussion from the microservices track at QCon Plus, held in May 2021. Track host Nicki Watt asks "What have we learned over the last decade of microservices?" The panelists included Chris Richardson, James Lewis, and Katie Gamanji. The discussion started with exploring how the meaning of "microservices architecture" has evolved over the past ten years; people often think it's about service size, but it's more important to design for replaceability. A key takeaway is that if your organization delivers software too slowly, adopting microservices will not fix that, and could make it worse.
Ballerina Swan Lake: 10 Compelling Language Characteristics for Cloud Native Programming
Ballerina is an open-source programming language purpose-built for cloud native programming and integration. The language has been designed to make it easier to use, combine, and create network services and thereby allows you to integrate distributed applications seamlessly. In this recent InfoQ article, Dakshitha Ratnayake explores how the Ballerina language has come a long way with significant improvements since the 1.0 release in 2019.
The latest Swan Lake release further simplifies building and deploying cloud-native microservices and applications through a network-aware and flexible type system, constructs for developing services and APIs (including REST, GraphQL, and gRPC), a sequence diagrammatic syntax, JSON support, and built-in concurrency among many other capabilities which will be explored in this article.
The InfoQ eMag: Operating Microservices
The companies that are successfully operating distributed systems use tools and techniques that address operational concerns of the individual microservices as well as for the whole system. This "Operating Microservices" eMag features content from InfoQ articles and presentations from the QCon Plus track of the same name, including: "GitHub’s Journey from Monolith to Microservices", "Solving Mysteries Faster with Observability", and "Resilience in Deep Systems".
Service Mesh Ultimate Guide - Second Edition: Next Generation Microservices Development
In this latest InfoQ Ultimate Guide, Srini Penchikala explores emerging architecture trends in the adoption of service mesh technologies, especially the multi-cloud, multi-cluster, and multi-tenant models. The guide discusses how to deploy service mesh solutions in heterogeneous infrastructures (bare metal, VMs, and Kubernetes) and explores application/service connectivity from the edge computing layer to the mesh layer.
How to Not Lose Your Job to Low-Code Software
The uptake of low code software is so strong that it will almost certainly make its way into your organization, regardless of whether you are working with monoliths, microservices, or serverless architectures. In this recent InfoQ article, Doug Hudgeon argues that most software engineers working in larger enterprises shouldn't be concerned about this because they are good at the things that low code software is not yet good at.
The key to surviving and thriving during this change is ensuring that your role encompasses responsibilities that low code can't do yet. If your role is solely focused on activities that low code software can perform you are at risk of being caught in a pinch point. Examples of pinch points include app/integration roles in small companies or small teams, and app developers working for app development companies.
Case Study
Turning Microservices Inside Out
Bilgin Ibryam's latest InfoQ article explores the concepts of turning microservices "inside out". To future-proof microservices, they must be designed with inbound and outbound APIs, where the data flows through, and a meta API that describes these APIs.
Ibryam argues that outbound events are turning into the preferred integration method for modern platforms such as cloud services, data sources, and even file systems. Custom-built microservices are not an exception, and emitting state change or domain events is the most natural way for modern microservices to fit uniformly among other event-driven systems.
The responsibilities and the importance of meta APIs are growing as their scope changes from describing synchronous APIs to also including asynchronous APIs. The meta APIs are expanding toward enabling faster development cycles by ensuring safe schema evolution through compatibility checks, notifications for updates, code generation for bindings, test simulations, and so forth.
Recent drivers such as cloud adoption and microservices architecture have accelerated the consolidation and community-driven standardization of open-source event streaming projects around Apache Kafka.
This content is an excerpt from a recent InfoQ article written by Bilgin Ibryam: "Turning Microservices Inside Out".
Missed a newsletter? You can find all of the previous issues on InfoQ.
Sponsored
|
|
"In a microservices system, culture and team design matters. In our research for this book and in our own implementation experiences we’ve learned an important truth: people and process are critical success factors. A microservices implementation is valuable when it gives you the freedom to make changes easily and quickly. In practice, however, change is a byproduct of your organization’s decision-making capability. If you can’t make quality decisions quickly, you’ll have a difficult time getting value from your microservices."
Learn more about this topic with selected chapters from our free eBook "Microservices Up & Running (By O’Reilly)".
|
|
Upcoming events
For practitioners by practitioners
QCon London 2022 (April 4-6,2022): Registrations are now open!
QCon London software development conference returns for 2022! Attend in-person on April 4-6, 2022 and deep-dive with world-class software leaders on the patterns, practices, and use cases leveraged by domain experts. Learn from the successes and failures of early adopter companies. Save £345 if you register before November 8th.
QCon Plus Session Spotlight (Nov 2, 2021): Remote Work - Developing Empathy and Tools Around Diversity & Inclusion
We have limited free places left for a special session on developing empathy and tools around diversity and inclusion with Wade Davis, former NFL player and the NFL’s first LGBT inclusion consultant working at the intersection of sexism, racism, and homophobia and now Vice President of Inclusion Strategy @Netflix. Register your interest to attend.
Senior software developers rely on the InfoQ community to keep ahead of the adoption curve. One of the main reasons software architects and engineers tell us they keep coming back to InfoQ is because they trust the information provided and selected by their peers.
We’ve been helping software development teams adopt new technologies and practices for over 15 years through InfoQ articles, news items, podcasts, tech talks, trends reports, and QCon software development conferences.
We hope you find this newsletter useful. If not, you can unsubscribe using the link below.
Forwarded email? Subscribe and get your own copy.
|
