Best of Monolith2022

  1. 1
    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.

  2. 2
    Article
    Avatar of communityCommunity Picks·4y

    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.

  3. 3
    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.

  4. 4
    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.

  5. 5
    Article
    Avatar of asayerasayer·4y

    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.

  6. 6
    Article
    Avatar of semaphoreSemaphore·4y

    When Microservices Are a Bad Idea

    Migrating from a monolith to microservices is not a simple task, and creating an untested product as a new microservice is even more complicated. A common reason developers want to avoid monoliths is their proclivity to deteriorate into a tangle of code.

  7. 7
    Article
    Avatar of quastorQuastor Daily·4y

    How Notion Sharded Their Postgres Database

    How Notion Sharded Their Postgres Database is a web/mobile app for creating your personal workspace. You can store notes, tasks, wikis, kanban boards and other things in a Notion workspace. Sharding adds an increased maintenance burden, constraints in the application code and much more architectural complexity. The Notion team looked at the hardware constraints they were dealing with.

  8. 8
    Article
    Avatar of dzDZone·3y

    Styles of Software Architecture

    This article summarizes the different styles of software architecture categorized as monolithic or distributed. As a developer, I have always thought that a distributed architecture is a solution that comes after having a monolithic architecture. As your application grows, deployments tend to be slower and spaced out over time due to security issues.

  9. 9
    Article
    Avatar of containiqContainIQ·4y

    Microservices Architecture | Ultimate Guide & Tutorial

    Microservices architecture is a software architecture pattern where each task performed by an application is handled by an independent application called a service. This service often manages its own database, and communicates to other services through events, messages, or a REST API. Microservices ease the task of building software, especially at scale.

  10. 10
    Article
    Avatar of honeypotHoneypot·4y

    When to use Microservices?

    Microservices is an excellent architectural style to address specific problems in large applications. It has worked for software giants in their early days, and it should still work for you as well. Building Microservices the right way is difficult. It requires more resource demand, high expertise, and effort involved to get them up and running.

  11. 11
    Article
    Avatar of hashnodeHashnode·4y

    Learn how to build a microservice using Node.js and RabbitMQ.

    Learn how to build a microservice using Node.js and RabbitMQ. This tutorial will teach you about microservices and how to create a simple e-commerce microservice architecture with two services; product and order. In the following section, we will look at some of the prerequisites for this tutorial. Make another folder for the routes, call it routes, then inside it, have a file routes.

  12. 12
    Article
    Avatar of communityCommunity Picks·4y

    Monolith vs Microservices: Which should you use

    Microservices as a software architecture has made its way into the development teams of popular companies like Netflix and Google. It offers flexibility, scalability and agility for the product or service you’re putting together. But that doesn’t mean it’s a perfect infrastructure, and a lot of companies both big and small still create monoliths.

  13. 13
    Article
    Avatar of communityCommunity Picks·4y

    Why Use Microservices — Breaking the Monolith

    Monolith Architecture is a software system called ‘monolithic’ if it has a monolithic architecture. It is a must for an organisation to move from a monolith to a microservices architecture to bring changes quickly, innovate fast, reduce time-to-market timelines and whatnot.

  14. 14
    Article
    Avatar of communityCommunity Picks·4y

    Microservice architecture is not a silver bullet

    A good architecture will allow a system to be born as a monolith, deployed in a single file, then grow into a set of independently deployable units, then all the way to independent services and/or micro-services. The dark side of microservices Microservice architecture has a lot of benefits, but sometime it's like a shrew. The clean, modular architecture shown earlier in figure 1.1 doesn’t reflect reality.

  15. 15
    Article
    Avatar of developercomDeveloper.com·4y

    Top 10 Microservices Design Principles

    Microservice architecture is a software architecture pattern where a system is designed as a network of loosely coupled services. This tutorial presents a discussion on some microservices design principles that will serve as guidelines to build scalable, high performance, fault tolerant microservices-based applications.

  16. 16
    Article
    Avatar of quastorQuastor Daily·4y

    Snapchat's Shift to Microservices

    Snapchat's Service Mesh Snapchat is an instant messaging application with 360 million daily active users from all around the world. Snap's shift from a Monolith to Microservices led to a 65% reduction in compute costs while reducing latency, increasing reliability and making it easier for Snap to grow as an organization. Snap used the Service Mesh design pattern where they had a data plane and a control plane.

  17. 17
    Article
    Avatar of awstipAWS Tip·3y

    From Monolith to Serverless

    AWS Lambda is the core component of the serverless platform, but there are a number of other services that are part of the broader serverless toolset. The key is to leverage as many of these services as you can to take care of the core primitive application layer concerns.

  18. 18
    Article
    Avatar of btrprogBetter Programming·3y

    How I Split a Monolith Into Microservices Without Refactoring

    How I Split a Monolith into Microservices Into Microservices Without Refactoring is how I split a monolith into microservices without refactoring. The idea of a modular monolith is definitely not new, but gains more attention as opposition to microservices. There are many ways (patterns) to organize a microservice architecture.

  19. 19
    Article
    Avatar of codemotionCodemotion·4y

    5 tips for Microservices good practices

    Microservices architecture makes the quantum leap in this industry possible: a flexible, scalable, and durable corporate architecture. In this article, we will discuss 5 tips for microservices and good practices that will allow you to achieve excellent outcomes with comparatively minimal effort. The advantages of microservices architecture over traditional monolithic design are numerous.

  20. 20
    Article
    Avatar of gitlabGitLab·4y

    Why we're sticking with Ruby on Rails

    When David Heinemeier Hansson created Ruby on Rails he was guided by his experience with both PHP and Java. With its solid, metaprogrammable Smalltalk heritage and good Unix integration, Ruby proved to be the perfect vehicle for DHH to fill that desirable bottom right corner of the table.

  21. 21
    Article
    Avatar of communityCommunity Picks·4y

    Bursting the Microservices Architectures Bubble

    A microservices architecture is an application development strategy that breaks application functionality into a suite of services. This is the opposite of what's known as a monolithic architecture, in which your entire application runs as a single process. There is no one right way to design a microservices app, nor are there specific tools, programming languages, or programming languages.

  22. 22
    Article
    Avatar of dzDZone·4y

    Monolith vs Microservices architecture

    Microservices architecture represents an application as a collection of small, loosely coupled services. Each service represents one business capability that makes it easier to locate the code. Monolithic architecture assumes several discrete functions composed into a single unit that is tested, deployed, and scaled as a whole.

  23. 23
    Article
    Avatar of algAlgolia Blog·4y

    How to successfully transition to headless architecture

    A headless tech stack with the best-of-breed building blocks benefits ecommerce companies with multiple strategic capabilities. There are many reasons to move from a monolith to headless architecture. These include the flexibility in building and customizing their ecommerce platform solution for a specific use-case.