Flexbase
  • Flexbase
  • Introduction
  • #JoyofCoding with Flexbase
  • Core Concepts
    • Flexbase
    • Flexstudio
      • Commands & Events
  • Thinking in Flexbase
    • Features and Modules
    • Designing APIs using Flexbase Control Flow
  • Sample Application
  • Solution Structure
    • Getting Started
      • Application
        • Introduction to Solution
        • Demo - Solution Generation
        • Solution Structure Overview
        • Architecture Overview
        • Clean architecture layer
        • Common Configurations
      • Features
        • Understanding Feature
        • Use Case
        • First Feature - Add Customer
        • Second Feature - Update Customer
        • Third Feature - Delete Customer
        • Query Features
  • Input Output Models
  • Messages
  • Domain
  • Pre Bus
  • Post Bus
  • Subscribers
  • Bus Gamma
  • Persistence
  • Hosting
  • Startup Code - WebAPI
  • Startup Code - Background Job
  • Endpoint - AppSettings
  • Bridge
  • Basic CRUD - Insert & Update
  • Introduction
  • View Generated API Definition in Swagger
  • Walkthrough Generated Code Insert
  • Walkthrough Generated Code Query GetById
  • Domain Model
  • Migration
  • AppSettings
  • Bus : How Basic Routing Config Works
  • INSERT : Input API Model
  • INSERT : Attribute Validation
  • INSERT : Plugin Validation
  • INSERT : Mapper
  • INSERT : Controller
  • INSERT : Services
  • INSERT : PostBus Handler
  • INSERT : PostBus Subscriber
  • INSERT : Demo In Action
  • QUERY : Output API Model
  • QUERY : Build and Fetch Pattern
  • QUERY : Demo In Action
  • Basic CRUD 2
    • Introduction
    • View Generated API Definition In Swagger
  • Walkthrough Generated Code Update
  • Walkthrough Generated Code Delete
  • Walkthrough Generated Code GetList
  • Walkthrough Generated Code Get Paged List
  • Update In Action
  • Delete In Action
  • GetList In Action
  • GetPagedList In Action
  • Konarch
Powered by GitBook
On this page

Core Concepts

Previous#JoyofCoding with FlexbaseNextFlexbase

Last updated 4 years ago

The builder knows the value of a solid foundation. S/he knows that the stability & utility of a building along with its ability to extend without compromising on safety depends on the foundation, beams, ducts & core structural elements of the building. But building these core structural elements itself is hard work. It takes a lot of time.

Imagine the delight of a builder who goes to a location, points out where he wants the building and tadaaa… the core structure is ready as per the specs of the building provided by the architecture. Now, that would be magic.

Flexbase, FlexStudio and FlexGen provide such a magical combination for creating a flexible core structure on top which any web API application can be built.

Flexbase is an architectural framework that provides architects a way of designing robust applications. FlexStudio and FlexGen take architect's design specification and magically build a high quality application structure.

FlexStudio is a tool that helps you turn client requirements into API design. This is like designing the building blueprint.

FlexGen is an architect's tool that takes more inputs from the architect on infrastructure and coding standards. Think of it as building material specification. Then FlexGen takes the FlexStudio blueprint and builds the core structure of the application as per Flexbase framework design specifications.

Now developers can get to work on the parts of application that add value to customer, without writing any framework code.

Yes, that’s right, zero framework code required and yet an application API that is enterprise ready.

What does it mean to you?

Huge productivity gains, ability to focus developer time on what matters to the customer, and still ending up with code that is performing, scalable, robust, distributed, secure, maintainable and extensible.

That’s the power of the Flexbase/ FlexStudio/FlexGen combo. It is built for Microsoft .NET development teams. Currently, Flexbase is available on .NET Core 3.1