Best of Architecture2022

  1. 1
    Article
    Avatar of communityCommunity Picks·4y

    Developer Roadmaps

    Developer Roadmaps roadmap.sh is a community effort to create roadmaps, guides and other educational content to help guide the developers in picking up the path and guide their learnings. The project is OpenSource, 6th most starred project on GitHub and is visited by hundreds of thousands of developers every month. We are working on a solution for teams. Help us shape the platform. The project has a solution to build and build a new software that will be available.

  2. 2
    Article
    Avatar of communityCommunity Picks·4y

    Netflix System Design- Backend Architecture

    Netflix accounts for about 15% of the world's internet bandwidth traffic. Netflix operates in two clouds Amazon Web Services and Open Connect (Netflix content delivery network) The overall Netflix system consists of three main parts. Zuul as its API gateway is built to allow dynamic routing, traffic monitoring, and security, resilience to The Netty handlers on the front and back of the filters.

  3. 3
    Article
    Avatar of freecodecampfreeCodeCamp·4y

    The Software Architecture Handbook

    In this article we'll talk about what architecture is within the software world, some of the main concepts to know about it. For each topic I'll give a brief and superficial introduction and code/pseudo-code examples. The most commonly used are REST, SOAP and GraphQl. Most often the HTTP protocol is used. But other protocols and content formats are perfectly possible.

  4. 4
    Article
    Avatar of pointerPointer·4y

    Fundamental Software Architectural Patterns

    Architectural patterns are essentially reusable solutions to common problems. Partitioning a system into separate layers, organizing components within them by related criteria, allows developers and teams to work better together. The scope is broader for the architectural patterns while design patterns represent a way to structure classes to build the best internal structure.

  5. 5
    Article
    Avatar of communityCommunity Picks·3y

    The Full-stack Software Design & Architecture Map

    The Full-stack Software Design & Architecture Map. How to Learn Software Design and Architecture is taken from Solid Book - The Software Architecture & Design Handbook w/ TypeScript + Node.js. The map is a little bit more detailed, and as a result, the map is more useful.

  6. 6
    Article
    Avatar of vercelVercel·4y

    Introducing Turbopack: Rust-based successor to Webpack – Vercel

    Turbopack: Rust-based successor to Webpack Vercel's mission is to provide the speed and reliability innovators need to create at the moment of inspiration. It's built on a new incremental architecture for the fastest possible development experience.

  7. 7
    Article
    Avatar of bytebytegoByteByteGo·3y

    Twitter Architecture 2022 vs 2012

    The diagram below shows how data is encapsulated and de-encapsulated when transmitting over the network. Each layer can rely on the headers for processing instructions and does not need to know the meaning of the data from the last layer.

  8. 8
    Article
    Avatar of gcgitconnected·4y

    React Best Practices for Software Design and Architecture

    React Best Practices for Software Design and Architecture has been working as a React developer since 2018. To keep an app productive and flexible we have to follow the software's architecture and design. We have to work on it effectively and change it without rewriting its base code.

  9. 9
    Article
    Avatar of devgeniusDev Genius·4y

    Top 10 Architecture Characteristics / Non-Functional Requirements with Cheatsheet

    Top 10 Architecture Characteristics / Non-Functional Requirements with Cheatsheet. Top 10 Architectural Characteristics covers most of the aspect of a large-scale project. You don’t need to accommodate all in your project; pick the most essential and knock it out.

  10. 10
    Article
    Avatar of communityCommunity Picks·4y

    Top 10 Microservices Design Patterns and Principles

    Microservice architecture is structured on the business domain and it's a collection of small autonomous services. Transaction management is the fundamental advantage of a shared database versus a per-service database. Event Sourcing is based on the idea that any change in an entity's state should be captured by the system. The persistence of a business item is accomplished by storing a series of state-changing events.

  11. 11
    Article
    Avatar of btrprogBetter Programming·4y

    The Clean Architecture — Beginner’s Guide

    The Clean Architecture is the system architecture guideline proposed by Robert C. Martin. This is one of the guidelines adhered to by software engineers to build scalable, testable, and maintainable software. The Dependency Rule states that the source code dependencies can only point inwards.

  12. 12
    Article
    Avatar of communityCommunity Picks·4y

    Introducing the Fleet Public Preview

    Fleet is our new distributed polyglot editor and IDE. It has been built from the ground up using our IntelliJ Platform on the backend and a brand new UI and distributed architecture. We’re still at the beginning of a long journey with Fleet, and we hope you’ll join us for what will be a great adventure.

  13. 13
    Article
    Avatar of communityCommunity Picks·4y

    DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together

    Ports & Adapters architecture identifies three fundamental blocks of code in a system. In most languages and in its most simple form, the Port will be an Interface, but it might actually be composed of several Interfaces and DTOs.

  14. 14
    Article
    Avatar of gcpGoogle Cloud·3y

    RESTful web API Design best practices

    A poorly designed API tends to create a similar experience for a consumer developer. Well designed APIs make it easy for consumer developers to find, explore, access, and use them.

  15. 15
    Article
    Avatar of communityCommunity Picks·3y

    Introduction to Micro-frontends

    Micro-frontends is the beginning of the micro frontends journey. The idea behind Micro Frontends is to think about a website or web app as a composition of features which are owned by independent teams. Each team should be able to choose and upgrade their stack without having to coordinate with other teams.

  16. 16
    Article
    Avatar of bytebytegoByteByteGo·4y

    EP30: Why is PostgreSQL the most loved database

    The ByteByteGo talent collective has 100 candidates live at this moment, and over 300+ applications from the best companies out there. The collective's members will have exclusive access to opportunities at high-growth startups and world-class companies such as Meta, Stripe, Snowflake, etc.

  17. 17
    Article
    Avatar of communityCommunity Picks·4y

    The Web’s Next Transition

    The web is made up of technologies that got their start over 25 years ago. AJAX was popularized as a term in 2005 and a lot of people started making HTTP requests in the browser.

  18. 18
    Article
    Avatar of communityCommunity Picks·4y

    Micro Frontends

    Micro Frontends is an architectural approach to frontend development with the idea of thinking of a project as a collection of features independently owned by different teams. Each team is cross-functional and develops its features end-to-end, from database to user interface.

  19. 19
    Article
    Avatar of quastorQuastor Daily·4y

    Airbnb's Architecture

    Jessica Tai is an engineering manager at Airbnb. She recently gave a fantastic talk on how Airbnb’s architecture has evolved over the years. Airbnb started as a Ruby on Rails monolith, then transitioned to a microservices architecture and has now migrated to a hybrid between micro and macroservices.

  20. 20
    Article
    Avatar of asayerasayer·3y

    7 Microservice Design Patterns to Use

    Microservice architecture is self-contained and wrap up around one business capability. It also refers to an architectural style for app development. The design is rapidly evolving and is one of the most important aspects of microservices. In the following sections, we’ll discuss seven important patterns.

  21. 21
    Article
    Avatar of communityCommunity Picks·3y

    Architecting an API Backend

    An API’s architecture often mimics how it is maintained and what the service accomplishes. An API may tap into various services to support its own backend, making the architecture stack deceptively complex. A similar ecosystem may exist fueling the components that make up an API itself.

  22. 22
    Article
    Avatar of communityCommunity Picks·4y

    Islands Architecture

    Islands architecture borrows concepts from different sources and aims to combine them optimally. Marko is an open-source framework developed and maintained by eBay to improve server rendering performance. Astro: Astro is a static site builder that can generate lightweight static HTML pages from UI components built in other frameworks such as React, Preact, Svelte,

  23. 23
    Article
    Avatar of freecodecampfreeCodeCamp·4y

    How to Create Microservices with FastAPI

    We just published a course on the freeCodeCamp.org YouTube channel that will teach you how to develop microservices app using FastAPI. FastAPI is a Web framework for developing RESTful APIs in Python. You will learn how to use RedisJSON as a Database and dispatch events with Redis Streams.

  24. 24
    Article
    Avatar of communityCommunity Picks·4y

    Popular Software Architecture Patterns

    Architecture patterns address issues like high availability, Scaling efficiency, Hardware performance bottlenecks, minimization of business risk, etc. Some of the popular Architecture patterns are Monolith Architecture Pattern. Service-oriented architecture is an enterprise-wide approach to software development that takes advantage of reusable software components.

  25. 25
    Article
    Avatar of communityCommunity Picks·4y

    The Guide to Modern Data Architecture

    This is an updated version of a post we originally published in 2020. We argue that core data processing systems have remained relatively stable over the past year, while supporting tools and applications have proliferated rapidly. We explore the hypothesis that platforms are beginning to emerge in the data ecosystem, and that this helps explain the particular patterns we’re seeing.