Best of ArchitectureSeptember 2021

  1. 1
    Article
    Avatar of devtoDEV·5y

    Clean Architecture on Frontend

    The Clean Architecture is a way of separating responsibilities and parts of functionality according to their proximity to the application domain. It is often referred to as a three-layer architecture, because the functionality in it is divided into layers. In this post we'll talk about what the clean architecture is in general and get familiar with such concepts as domain, use case and application layers. Then we'll discuss how this applies to the frontend and whether it's worth it at all.

  2. 2
    Article
    Avatar of itnextITNEXT·5y

    Clean architecture - making Node.js API shine!

    Clean architecture is a software design philosophy that advocates for the separation of layers of code. The separation of elements lends itself to easier testing, where we can test each module independently of others. In order to be flexible with project dependencies, use dependency injection mechanisms. Code on the inner layers can only move from the outer layers.

  3. 3
    Article
    Avatar of dzDZone·5y

    7 Microservices Best Practices for Developers

    Microservices are an improved software architecture that allow you to deploy and scale faster. With these benefits, we have a new set of challenges, including inter-service communication, security, and scalability. These best practices will help you create a robust, easy-to-manage, scalable, and secure system.

  4. 4
    Article
    Avatar of netflixNetflix TechBlog·5y

    Practical API Design at Netflix, Part 1: Using Protobuf FieldMask

    Never rename fields when FieldMask is used. If a field is renamed, the backend should be able to support new and old field names until all the callers migrate to the new field name (backward compatibility issue) Deprecate a field and create a new field instead of renaming.

  5. 5
    Article
    Avatar of dzDZone·5y

    Microservice Roadmap

    With the rise of social media, fast internet, etc. monolithic applications need to deal with a tremendous majority of changes. One of the solutions to boost the application flexibility, scalability, and so many other concerns is to follow a flexible architecture like microservice-based architecture. I decided to make this journey more clear by defining a road map.

  6. 6
    Article
    Avatar of towardsdevTowards Dev·5y

    Creating a gateway service with node js, typescript and fastify.

    gateway is an infrastructure layer that sits at the front of all your back-end micro-services. It is a node network, a key stopping point for data on its way to or from other networks. Since we are using typescript, we have a lot of configuring to do before hand. We are going to make use of the micro- services architecture.

  7. 7
    Article
    Avatar of tshThe Software House·5y

    Microservices security patterns – tutorial with examples

    Microservices help you deliver code faster and make it efficient for teams to split work without conflicting with each other. A security “hole” in even one service can impact the entire application. Here is a list of 8 microservices security patterns that are commonly used for more secure microservices.

  8. 8
    Article
    Avatar of itnextITNEXT·5y

    [BUILD] BFF Pattern with Go Microservices using REST & gRPC.

    Let’s build dockerized Go microservices demonstrating the BFF pattern with REST and gRPC. Bind it to the UI and deploy everything on AWS EC2. (Also has Kotlin & Java versions) TL;DR: Github Go, Github Kotlin, Github Java, Github UI BFF, a.k.a. “Best Friends Forever’ pattern is a well-established architectural…

  9. 9
    Article
    Avatar of codecentriccodecentric·5y

    AsyncAPI – Documentation of event- and message-driven architectures

    AsyncAPI is a new counterpart for event- and message-driven architectures. It was developed on the basis of OpenAPI and is more agnostic in its approach with regard to possible protocols. In the use case, a message regarding an order is to be transmitted from a producer via a queue to a consumer.