Ardalis·2yFrom Microservices to Modular Monoliths
Struggling with the complexity of microservices? Consider migrating to a modular monolith. This approach maintains the gains from breaking up a legacy system without dealing with the issues of a massively distributed system. A modular monolith can simplify management, reduce latency, and keep communication efficient among well-defined modules. However, such a migration needs careful planning and execution.
Venture Beat·1yWhy microservices might be finished as monoliths return with a vengeance
Many organizations are re-evaluating the trend towards microservices and returning to monolithic architectures. This change is driven by the difficulties encountered during the transition, such as defining domain boundaries, managing deeply coupled data, and handling complex data migrations. Despite the theoretical advantages of microservices, practical implementation challenges often outweigh the benefits, leading to issues like increased system complexity, data integrity problems, and unclear team ownership.
ByteByteGo·2yThe Scaling Journey of LinkedIn
LinkedIn faced challenges in scaling its platform as its user base and content grew. They adopted a distributed and partitioned graph system, built a search service using Lucene, and migrated to a service-oriented architecture. They also used caching and implemented data collection with Kafka. Additionally, LinkedIn developed tools like Rest.li for API development, introduced super blocks to manage multiple services, and implemented multi-data center support. Other advanced developments included real-time analytics with Pinot and managing authorization at scale.
Community Picks·2yInteresting Facts about Software Architecture Styles You May Not Know
This post explores various software architecture styles and their relevance in today's development landscape. It discusses the difference between architectural styles and patterns, the continued use of monolithic architecture by some companies, the advantages of microservices architecture, the history and benefits of event-driven and serverless architectures, the compliance benefits of edge computing, and the rise and relevance of peer-to-peer architecture.
Java Code Geeks·2yA Beginner’s Guide to Architectural Patterns
This post explores eight different architectural patterns commonly used in software development, including Monolithic Architecture, Microservices Architecture, Layered Architecture, Event-Driven Architecture, Service-Oriented Architecture (SOA), Model-View-Controller (MVC), Serverless Architecture, and the Repository Pattern.
Community Picks·2yRefactoring a monolith into microservices
This post is part of a series on designing, building, and deploying microservices. It focuses on the process of refactoring a monolithic application into microservices using domain-driven design and various decoupling strategies. It also discusses the challenges and considerations for managing a monolithic database, handling distributed transactions, and implementing interservice communication.
