Introduction
There are three types of features every customer recognizes - the expected, the regular and the exciting.
For example the latest Mercedes Benz and BMW car ads highlight, multi contour massaging seats, magic body control with sensor driven suspensions, automatically pulling in and out of garage and narrow parking spaces, operating the dashboard through hand gestures, talking to the car - this is the exciting stuff.
They don’t advertise that the brakes will work or that the car starts when you turn the ignition on. These are expected features. Somewhere in between are the regular features. Some standard features the customer explicitly asks for. The exciting features are often unstated, yet these are the features that create a wow, and makes the customer a fan.
Technology customers are no different.
Software applications have become very complex. They need to have high performance, scalability, maintainability, extensibility, security, distributed design, fail-safe mechanisms... the list goes on. These quality attributes make application plumbing complex.
You end up putting best resources where complexity is high. But the irony is, from a customer’s point of view, all the complex quality attributes are expected features. ("That's why it is called software and not hardware")
It is useful to examine how much of the architects' and top developers’ time goes into making these expected but complex features.
Unfortunately, the development team keeps reinventing the “quality attribute (NFR) requirements wheel” again and again and again in every new project, in their own unique way.
The business domain analysis takes a back seat. This leads to faulty applications with incomplete features.
The problem doesn't stop there. Once the project pressures mount, the quality attributes suddenly take a backseat and Big Ball of Mud syndrome takes over.
The story of every well intended project is - the exciting stuff is always just a couple of releases away.
Flexbase helps you solve this problem.
Flexbase takes essential non-functional requirements and packages them in a layer on top of Microsoft .NET:
- 1.Distributed architecture with out-of-the-box async and parallel processing to solve scalability issues
- 2.Plug-in based development model that solves extensibility issues
- 3.Enterprise service bus to solve robustness and performance issues
- 4.Standards driven code that is dead easy to understand to solve maintainability ,And way more.
API developers write code on top of Flexbase just like they would in .NET Core. Only now, they can put all their focus and energy on the business domain and on building stuff that is actually valuable and exciting to the customer. Let Flexbase take care of the expected.
Whichever architecture style you use microservices, event driven, domain driven design, or a monolith; or whether you have deployed applications on-premise or on the cloud - flex just works.
Are you on Azure? Flexbase is designed to integrate tightly with Azure PaaS services - SQL PaaS, Azure functions, Table Storage, Azure Service Bus, Azure AD and more.
Let your dev team stop working on the chassis of the car and work on something exciting that actually makes a difference to your customer.
Flexbase - make the leap from expected to exciting.
Last modified 1yr ago