Best of ArchitectureJune 2023

  1. 1
    Article
    Avatar of cloudnativedailyCloud Native Daily·3y

    10 Microservice Patterns Software Engineers Should Know

    Building scalable software requires a software engineer/architect to pick the right architecture. Monolithic architecture is usually the first choice in mind for most engineers because it is easy and does not have to deal with the distributed system complexity because a whole application is in the same giant codebase when dealing with agile software delivery.

  2. 2
    Article
    Avatar of freecodecampfreeCodeCamp·3y

    Key Computer Science Concepts Every Software Engineer Should Know – and How to Learn Them

    The more fundamentals you know, the less you will struggle learning new things. There are 10 core subjects which, if you learn them, will give you a solid foundation. The book I recommend to learn programming is Structures and Interpretations of Computer Programs (SICP) The book is free and has a set of MIT lectures.

  3. 3
    Article
    Avatar of communityCommunity Picks·3y

    Is React Having An Angular.js Moment?

    React and Next.js teams have been promoting Server Components, a new way to build web applications that don't fit with most existing React apps. Server Components is entirely different from client-side JS, despite the fact that the base - JSX - remains the same.

  4. 4
    Article
    Avatar of cloudnativedailyCloud Native Daily·3y

    Scaling Microservices: A Comprehensive Guide

    Scaling Microservices: A Comprehensive Guide How to tackle challenges in scaling microservices. Scaling microservices can pose significant challenges and tools you can use to prevent them. Service discovery, load balancing and inter-service communication are the 3 main aspects you need to consider.

  5. 5
    Article
    Avatar of discdotDiscover .NET·3y

    Code Review & Refactoring to a better design

  6. 6
    Article
    Avatar of discdotDiscover .NET·3y

    "Clean Architecture" and indirection. No thanks.

  7. 7
    Article
    Avatar of redislabsRedis·3y

    Microservices and Containers Explained… Using LEGOs

    Microservices are small, independent components that you can combine to build larger applications. This is a stark departure from the traditional monolithic architecture, where an application is developed as a single unit. Microservices can communicate with each other through APIs, which enables the application to function as a cohesive whole.

  8. 8
    Article
    Avatar of discdotDiscover .NET·3y

    Biggest scam in software dev? Best Practices.

    CodeOpinion Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free. What’s the biggest scam in tech that is deemed acceptable?

  9. 9
    Article
    Avatar of tshThe Software House·3y

    Node.js interview questions, tips, trends

    Node.js has been one of the most consistently in-demand technologies for the past couple of years. There will be some Node interview questions too, but keep in mind that memorizing the questions and answers alone won’t get you far. The fundamentals are what make the most difference.

  10. 10
    Article
    Avatar of cloudnativedailyCloud Native Daily·3y

    10 Tools for Scaling Microservices

    Helios Helios is an observability tool that plays a crucial role in scaling microservices. It provides real-time visibility and insights into the performance and health of the system. Helios supports distributed tracing to help you understand the flow of requests across different microservices in your application.

  11. 11
    Article
    Avatar of freecodecampfreeCodeCamp·3y

    What is Infrastructure as Code? Explained for Beginners

    Infrastructure as Code (IaC) is a way of managing your infrastructure like it was code. This gives you all the benefits of using code to create your infrastructure, like version control, faster and safer infrastructure deployments. The article will cover the different infrastructure as code tools available as well as declarative vs imperative code.

  12. 12
    Article
    Avatar of nextNext.js·3y

    Next.js App Router Update

    Next.js App Router Update: The App Router represents a new foundation for the future of next.js. We want you to know that we are not yet satisfied with the experience of using the App Router and it is our top priority moving forward. We are exploring further opportunities to make incremental adoption even easier.

  13. 13
    Article
    Avatar of communityCommunity Picks·3y

    Building a Resilient Three-Tier Architecture on AWS with Deploying MERN Stack Application

    Building a Resilient Three-Tier Architecture on AWS with Deploying MERN Stack Application on AWS. The project will use multi-region deployment, one will be the primary region and the second will be for disaster recovery. The architecture of the project is a software architecture pattern that separates an application into three layers.

  14. 14
    Article
    Avatar of kdnuggetsKDnuggets·3y

    Ten Years of AI in Review

    The last decade has been a thrilling and eventful ride for the field of artificial intelligence (AI). Modest explorations of the potential of deep learning turned into an explosive proliferation of a field that now includes everything from recommender systems in e-commerce to object detection for autonomous vehicles and generative models.

  15. 15
    Article
    Avatar of cloudnativedailyCloud Native Daily·3y

    Event-Driven Application with Spring Boot and Apache Kafka

    The system reacts based on the event instead of the regular making request and waiting for a response sequence. This allows systems to communicate with one another asynchronously and reliably. Even when the system is down it’s still able to process the request when it comes back online.

  16. 16
    Article
    Avatar of attiAT&T Israel·3y

    The Software Design Principle that we all agree on — Part I

    Part I Software design principles and frameworks are guidelines of good software development. Kfir Ezekiel: In practice, design discussions can often be a source of immense frustration for those involved. We will delve into the rich history of design principles in search of a unifying design principle.