Modular system architecture

I am trying to implement modularity in my POS system to allow third parties to make some modules / plugins / additions. I started to implement SPI and API, my question is this: should the data access in the database be this way or do I need to provide a service?

At this point, you may have noticed that I have little experience with this, so any advice on this topic is good

Edit: a little more information. My system has a user system that theoretically checks credentials to access any part of the system, a mysql database written in Java. My modules reliably need access to some tables in the database, access to the main menu, I don’t know what else I can say, but my question is more abstract about how api should be.

early

PS sorry if my english is bad

Octavio Ruiz

+3
source share
1 answer

In general, software systems are (usually) divided into β€œlayers” (such as user interface, business logic (BL), data access level (DAL), etc.). These layers also provide natural places for integration. So that...

access to data in the database to be this way or do i need to provide a service?

, , , API. , -, , . , , , .

:

  • , ( ); (, ).
  • .

- , StackOverflow .

, SOLID, , , S, O, D, .

( "D" ) . "" , -, , : , .

Java ( ), .Net , : Managed Extensibility Framework (MEF).

, , .

+2

Source: https://habr.com/ru/post/1768852/


All Articles