Monolithic vs Microservices, which is use for frappe now

Frappe Framework
1

I do not know which architecture is Frappe? Monolithic vs Microservices ? thks for your answer

2

It still Monolithic!

Even theres the concept of Apps frappe is far away of microservices

3

@max_morais_dmm
So, the development of an application with a large and highly complex application will be difficult to meet, right

4

Really hard to say!

I have a customer that is a telecom, with more than 250 services connected to ERPNext, about 10000 transactions daily, with zero downtime since 2014!

5

@max_morais_dmm

Thanks for taking the time to answer, perhaps the best thing I need to do to find this answer is that I will try, hihi :100:

6

It used to be strict monolithic, but now though no microservices, it is going away from monolithic, IMO.

Different apps have different code for almost same thing.

Version naming of different apps follow different policy.

For most of the software main/master branch is the default, but here mostly develop branch is the default branch. I hope there must be a valid reason to do so. May someone shed some light on this.

Standard contact is not used by all apps, many apps do capture address in their own way.

Installation apps be becoming pain.

@Jannat_Patel and @Ritvik_Sardana

Are you thinking of having co-operation / integration between Education and Learning Apps.

There may be 3rd app having common base for two, and then on top of that user may install any of these app, with no duplicate data.

@rmehta

Am I missing something?

1 Like
7

It depends. Stackoverflow is a monolith app :slight_smile: Monolithic architecture is not so bad and if you want to still implement microservices architecture you can. There are several ways to do it.

Highlevel approach:

  1. Write all your logic as Microservices
  2. Use webhook function to delegate the logic to microservices
  3. Use external jobs to process batch data
  4. Use Virtual Doctypes :slight_smile:
8
  • Optionally depend on TCP/GRPC/MQTT, something faster than HTTP.
  • Experiment with events pub/sub instead of HTTP request/response.

EDIT:

There is also an approach of one app one site/api where each frappe-bench site will only have one “business domain” frappe app installed and user identity is propagated through separate identity provider (OAuth2/OIDC). Something like this:

It gives you separate DB per app.

1 Like