Fix the following errors:
News
The role of a modern software architect is continually shifting. Gone are the days where the architect title was a position earned purely by seniority - the range of topics and the velocity at which they change within the software development industry means that continual research, learning and experimentation with new technologies is now vital for success in this role. InfoQ strives to facilitate the spread of knowledge and innovation within this space, but we acknowledge that it can be difficult for a busy architect to digest all of the content being produced. Accordingly we have created this newsletter, written by a team actively involved with the architecture and delivery of real-world software applications.
We aim to curate and summarise key learnings from news items, articles and presentations created by industry peers, both on InfoQ and across the web. We will strive to keep readers informed and educated about emerging trends, peer-validated early adoption of technologies, and architectural best practices.
Architects' Newsletter
A monthly overview of things you need to know as an architect or aspiring architect.
Stay on top of trends with just one email per month. Written by architects for architects.
Streaming Microservices: Contracts & Compatibility
In a world of microservices that communicate via unbounded streams of events, schemas are the contracts between the services. Having an agreed contract allows the teams developing those services to move fast, by reducing the risk involved in making changes. At QCon New York, Gwen Shapira discussed the challenges of compatibility, and introduced possible solutions to manage this, such as a centralised schema registry, which stores a versioned history of all schemas, provides multiple compatibility settings and allows evolution of schemas according to the configured compatibility setting.
An open source realisation of this pattern is the Confluent Schema Registry, which provides serializers that plug into Kafka clients that handle schema storage and retrieval for Kafka messages that are sent in the Avro format.
Subscribe to the monthly newsletter to read more.
The Microservices Journey from a Startup Perspective
Microservices come with complexities like multiple independent services, operational & communication complexity, partitioned data, and the complexity of eventual consistency. Susanne Kaiser, CTO at Just Software, spoke at QCon New York 2017 about the transformation process her team went through to transition from a monolithic application architecture to microservices model.
Kaiser’s key learnings included: not having an explicit infrastructure team will slow down the migration; decomposing big chunks of system functionality upfront is not recommended; and be prepared for the transition to a new way of building software to take longer than originally anticipated.
Subscribe to the monthly newsletter to read more.
by