New & Notable


Pros and cons of monolithic vs. microservices architecture

Developers interested in shifting to microservices should seriously consider whether a monolithic approach may be the smarter choice. Here are the key factors to consider.

Problem Solve

Is low-code the answer to microservices complexity?

Software developers are in a constant battle with complexity. Microservices hold promise as ready-to-assemble app components, but low-code development might be a better approach.


How to choose the right integration method between apps

APIs are a safe, reliable way for applications to execute a workflow. But they're not always available. Here's how to craft an integration strategy around APIs, RPA and even people.


The monolith isn't dead, and here's why

Don't rush to break up a monolith too quickly without considering what you might lose in the process. We examine why a monolithic architecture is sometimes the smarter choice.

Have a question for an expert?

Please add a title for your question

Get answers from your peers on your most technical Application Architecture challenges.

You will be able to add details on the next page.

Find Solutions For Your Project

Pro+ App Architecture Downloads

View All

Application Architecture Basics

View All Get Started


Videos, Podcasts, Photo Stories and Infographics

Sections from across SearchAppArchitecture

  • News

    View All
  • Application development planning

    GraphQL vs. REST choice steers microservices development

    GraphQL vs. REST: That is the question as teams tackle microservices architecture design, and at Pantheon, the choice came with both business boons and technical debt.

  • Container orchestration

    Pivotal tools tackle Kubernetes complexity

    Pivotal has released several tools to help developers and operators address Kubernetes complexity, as enterprises increasingly adopt the popular container orchestration system.

  • Enterprise application integration

    Netflix taps GraphQL for content engineering

    When the Netflix content engineering team chose a data query language for a new system to pull data from a variety of back-end services, they passed over REST to go with GraphQL.