Key Concepts

The MemberJunction architecture is documented across several sections of this website. These concepts are important to understand before you go too far in implementing MemberJunction for your organization. We recommend taking some time to browse through this content to fully understand these key concepts.

A central concept for MJ that is used to create an abstraction layer between the implementation of the provider and the rest of the infrastructure and also enable higher order work in an application by automating many lower level aspects of the CDP and application development

This is a central and crucial part of MJ to fully understand. CodeGen is used to maintain the MJ Metadata as well as generate APIs, UI components and more.

MJ has a specific approach to database design that is important to understand as you educated yourself on the framework and plan your implementation.

A modern and flexible API approach that MemberJunction uses for its API layer

MemberJunction implements a Provider style of architecture which makes code largely independent of where it is executing. For example, being able to run the same business logic for validation in a browser and on a server.

Overview of how business logic is handled in the MemberJunction architecture.

A key concept in MJ that improves reusability, encapsulation and tier-independence.

This application is a convenient utility that can be used to visualize and browse data across all entities within MemberJunction. It also serves as a component library for building other applications as well as a more sophisticated sample application that can be used to build other apps.