mORMot Open Source

Hi Ab, I found out that the problem is related to my mounted where clause.
It does not work:
IdWooCommerce>0 and (SyncSupraWoo=? or SyncSupraWoo is null)

but it works:

SyncSupraWoo=? or SyncSupraWoo is null

I can't use clause and with or.

hi ab,
Maybe I expressed myself wrongly. When I say monitor I am referring to the ExecuteRetrievePendingAndSetProcessing method which is checking the value of a given field to return true or false. that's the concept of pendingtask isn't it? or am I mistaken?

Hi, Ab

The TDDDMonitoredDaemonProcessRest class serves to monitor the state of some field in a table and perform an action on the value contained in this field, right?
When the change in the value of this field being monitored occurs via trigger directly in the database, this change is not seen by TSQLRecord.
This way, when this SyncSupraWoo field is receiving a value directly from a trigger in the database, fPendingTask is never created. Understood?

Hi Ab, I checked the logs and there was nothing to indicate a problem, so I updated the versions of fcp installed on jenkins and it started working again. Thanks.

Hi uian2000, is that I'm actually using master / slave replication as a way to work on persistent domain events, something that is recommended by Ab himself.

Hi Ab,
yes i can use replication via websocket with the proper infrastructure, however for that i would need to expose my RestServerDB in a TSQLHttpServer for this is not it? Wasn't the purpose of the post I indicated in the link just to isolate the RestServerDB and not expose them directly to TSQLHttpServer?

Would the TDDDRepositoryRestFactory builder call each request from the rest then?

Thanks Ab, I ended up following this same line of thought this weekend and ended up implementing it, my dbs were already separated by int64 so I separated them via root uri, really the advantages are many. The fact that you can cache an entire layer is fantastic. I'm only concerned with callbacks now. since before each callback only supports the subscribers of the rest layer of the specific database. But now everyone will be signed to a single layer, right? Thanks to all tbo, vitaly and ab for the answers, they clarified many of my questions.

Hello Vitaly ,  let me see if I understand. Are you suggesting that I do not expose my TSQLRestServerDB via TSQLHttpServer but use a TSQLRestServerFullMemory that connects as a client of my TSQLRestServerDB? Is there a way to expose my rest server layer without coupling it to a TSQLHttpServer?

Hi Ab, thanks for the reply, my idea was as follows: each service of mine is a different server. In each service I have several tenants using this service. This architectural pattern is already known (Multi-tenant APP with Simple tenant Database)
This inside the mormot I can easily separate by the instance of TSQLRestServerDB where each tenant of mine is a specific root.
The result of this is that I can in each service of mine (when I say service I am referring to a business object) with several databases linked to this service

I will explain using the classes of the mormot itself to facilitate the understanding:

TSQLHttpServer(this represents my business service)--->TSQLRestServerDB1,TSQLRestServerDB2,TSQLRestServerDB3 ....(this represents the tenants' databases)

on another server

TSQLHttpServer(this represents my business service)--->TSQLRestServerDB1,TSQLRestServerDB2,TSQLRestServerDB3 ....(this represents the tenants' databases)
Do you notice that I solve the isolation of the tenent in the architecture of the mormot?

I have a common service that does what you suggested, returns the ideal root for the ideal server. However, when a new tenant starts using a service that he was not part of on a server (in the case of hiring a product of ours) I need to instantiate a TSQLRestServerDB ideal for that tenant at runtime, if not he does not even exist in the other service.
The question I asked earlier is whether I would be making this architecture somewhat complicated when it is unnecessarily complicated?
If I am dealing with the tenant's isolation in the model, it would not be easier to develop or to maintain it later?

In this way:
TSQLHttpServer(this represents my business service)--->TSQLRestServerDB(here would have all tenants isolated by the model)

Thanks macfly,

Thanks, ResultAsJSONObjectWithoutResult was really missing.

I'm using fDaemon.Rest.Update (). The strange thing is that the two fields that I change in this update are not the one that contains the html content. I am using a structure similar to the dddInfraEmailer examples to send emails.

Hi Ab, thanks for the reply. I changed it to RawUTF8 and the error persists. I'm using sqlite to persist the value of this field. If I have to put the html too big it gives the same problem. Is there any text size limitation for sqlite? do I need to use some kind of compression? The strange thing is that I already recorded json much larger than this html in a RawUTF8 field and I had no problems. I forgot to comment in the previous post, persistence occurs in a DaemonProcess, I created a structure similar to what you have in dddInfraEmailer to send emails, this field content is the body of the email.

I tried to use it as the original example also with MessageCompressed: TByteDynArray and if it is this very large html in the exception body

Oi @ mdbs99, the ideal would be to let the tenants' servers do this management. But callback listeners do not connect directly to these servers, they pass through the gateway. Only he knows which tenant server to request.

Ok Ab, thanks for the clarification, I used a record array that contains a list of callbacks and their UIDs. It worked at first I still need to test in thread. Is this architecture that I put in place valid? Sometimes I think I could solve everything with a single server.

Hi Ab, it is because my TSQLRestServer works as a gateway. is a TSQLRestServer for several TSQLRestServerDB on another server, and each TSQLRestServerDB is a tenant. I cannot answer calls to all tenants through a callback array. Senao will have a tenant receiving a response from another tenant. And that is not desirable in my architecture.

Hi ab, I don't know if I expressed myself well, I'll try to describe my architecture:

- (Server 1) I have a TSQLHttpServer that works as a gateway. This is working on port 8888 right.
- (Server 2) this server is a client of domain servers via interface. Then on another server I have the following architecture working on port 8889.:
TSQLHttpServer.Create(GetPort,[FServerTenent1,FServerTenent2,FServerTenent3,
   FServerTenent4]);

So with each request that on server 1 I know which client to instantiate from server 2 because I receive information that distinguishes the servers in the jwt key.
Any and all requests are made by the user on server 1 and not on serverv 2.

Now I'm thinking how to implement a callback server on server 1 and I need to distinguish one client from another on server 2. If I go through a simple array of callbacks, all my connected tenants will receive responses, and this cannot happen. I must propagate messages differentiating one tenant from the other.

I thought about using a record array to control this. Or am I thinking too wrong about it?

Thanks Ab, it clarified a lot. Thanks to everyone who responded, I will proceed with some .net client-side resolutions now.

Okay, what about an expired token? What to do?

Hi Vitaly, thanks for the reply, I understand your suggestion, but my client is not a TSQLHttpClient but an Asp.net client. How do you think this token renewal policy would work in this scenario?

Hi Ab, it's true, I didn't think this before, . A simple free on FDocs solved the problem. Thank you very much Ab and MacFly. a lot of it. I found it a bit complicated to keep this serialization with abstraction, is there a better way?

Hi Macfly, this field exists, I just omitted it because I don't consider this class more fields like name, email, phone and one of them is the type. The TDocs abstraction classes also have more properties. I just omitted it for the example. But really Macfly I need to be testing the type whenever I need to recover this class, but my problem is being serialization. I managed to serialize the abstraction using TJSONSerializer.RegisterCustomSerializer and it looks like this:

class function TPerson.DocsClassReader(const aValue: TObject;
  aFrom: PUTF8Char; var aValid: Boolean; aOptions: TJSONToObjectOptions
  ): PUTF8Char;
var V: TPerson absolute aValue;
    Values: array[0..4] of TValuePUTF8Char;
begin
  result := JSONDecode(aFrom,[
  'Name',
  'TypeDocs',
  'Docs'
  ],@Values);
  aValid := (result<>nil);
  if aValid then begin
    V.FName := Values[0].ToUTF8;
    v.FTypeDocs:= TTypeDocs( Values[1].ToInteger);
    case V.FTypeDocs of
     tpPF:begin
     V.FDocs:= TDocsPF.Create; //here is the problem there is a memory leak
     ObjectLoadJSON( V.FDocs,Values[2].ToUTF8);
     end;
     tpPJ:begin
     V.FDocs:= TDocsPJ.Create;
     objectLoadJSON(V.FDocs,Values[2].ToUTF8);
     end;
    end; 
   

  end;       

It doesn't work, I always rely on the examples to start implementing with mormot. I create the user by the same mormot, everything goes ok, so much so that when I connect with mongo compass for that created user it works.Is it something in my sources?

Cool Ab,
can i then use TSQLRestServer.ServiceContainer.InjectResolver to resolve this as an internal service? Would you like to call this implementation just by solving its interface, because its construction is complicated, or is it better to solve it with a dedicated constructor? It would be an internal service, I don't need to expose it as rest.