Skip to main content
Version: 1.2

Philosophy

logo

Motivation - Why another framework?​

We created the features in our Node JS + Parse server project. What was an experience to ease the backend development quickly became a good practice that helped us keep a clean codebase. They worked so well we decided to streamline their integration with the code base for future projects. We were inspired by the powerful ways NextJs improved the React experience by providing an efficient template on top of it. Yet we did not want to hide the Parse Server framework behind ours as we truly love Parse. Servable allows to tap into all the existing and upcoming Parse features and yet it dramatically simplifies the development process. A well designed Servable project will comprise almost nothing more than the actual models and business logic of the platform, other repetitive functions and logics will use existing features implemented by the community or entreprise-private features.

Principles​

Convention over configuration​

Convention over configuration (also known as coding by convention) is a software design paradigm used by software frameworks that attempts to decrease the number of decisions that a developer using the framework is required to make without necessarily losing flexibility and don't repeat yourself (DRY) principles.
Wikipedia

Don't repeat yourself (DRY)​

"Don't repeat yourself" (DRY) is a principle of software development aimed at reducing repetition of information which is likely to change, replacing it with abstractions that are less likely to change, or using data normalization which avoids redundancy in the first place.
Wikipedia

Feature first​

When refactoring code we can either group our files by the technical function they provide or the feature they provide the end user. Servable chooses to emphasize on features the most as it yields substantial benefits for the teams and the orgranization as a whole.

Read more

Extreme refactoring​

Refactor mercilessly
Servable takes refactoring to the extreme by decluttering the app from the underlying features that different models use into a single package called feature. Contrarily to a middleware or an extension, a feature is a high level, conventioned, predicatable and versioned piece of code that provides a functional feature. Extreme refactoring with features yield extreme reusability from the ground-up by instilling a feature driven culture in your teams.
Variable → Function → Class → Module → Extension → Feature
Extreme refactoring

Functional programming​

(over object programming)

Functional programming is a paradigm of building computer programs using expressions and functions without mutating state and data. By respecting these restrictions, functional programming aims to write code that is clearer to understand and more bug resistant.

Liskov substitution principle​

Let q(x) be a property provable about objects of x of type T. Then q(y) should be provable for objects y of type S where S is a subtype of T.

Other influences​

Should you use Servable?​

Servable is likely a good fit for you if

  • You want to group the development of your server by capacity
  • You want to reuse a capacity (feature) over different models without copying it over and over
  • You want to make that capacity available throughout your organization or publish it on the web
  • You are building a new platform from scratch but you don't want reinvent the wheel for the usual suspects: social interactions, versionning, data consistency over deletion

logo

Simon Buret, The blessings, 2022