Sounds very cool!
+1
]]>SpringCloud is indeed interresting.
Currently, with mORMot 1.18 there are the basic bricks of daemons setup and administration - and they are used in production - but they need to be glued by some proprietary code.
With mORMot 2, we would like to offer something similar. We will integrate the daemons and their hosting, with a centralized administration tool. Including remote real-time logging, and remote database access - which are features not available in SpringCloud.
We will focus on MicroServices definition and hosting.
We will define services from a set of settings files, as part of the source code, to setup the daemon name/ports/persistence features.
Then hosting would be as simple as assigning daemons to hosts. Hosts will be first regular Windows and Debian/Ubuntu Linux instances (since we know them very much) but could later on be some Cloud providers (even if the fully-embedded nature of mORmot MicroServices doesn't make cloud services useful). A nginx front-end (with Let'sEncrypt TLS) would be automatically setup on each Linux host - or as stand-alone frontend to Windows hosts. Hosts will be monitored in real-time (processes, memory, network). Also executable updates will be done remotely.
Security will be offered using asymetric public/private keys, via mormot.core.ecc.pas.
We did not start to work on it yet. But it is something we will implement, since we need it for the future.
Sounds very cool!
]]>Currently, with mORMot 1.18 there are the basic bricks of daemons setup and administration - and they are used in production - but they need to be glued by some proprietary code.
With mORMot 2, we would like to offer something similar. We will integrate the daemons and their hosting, with a centralized administration tool. Including remote real-time logging, and remote database access - which are features not available in SpringCloud.
We will focus on MicroServices definition and hosting.
We will define services from a set of settings files, as part of the source code, to setup the daemon name/ports/persistence features.
Then hosting would be as simple as assigning daemons to hosts. Hosts will be first regular Windows and Debian/Ubuntu Linux instances (since we know them very much) but could later on be some Cloud providers (even if the fully-embedded nature of mORmot MicroServices doesn't make cloud services useful). A nginx front-end (with Let'sEncrypt TLS) would be automatically setup on each Linux host - or as stand-alone frontend to Windows hosts. Hosts will be monitored in real-time (processes, memory, network). Also executable updates will be done remotely.
Security will be offered using asymetric public/private keys, via mormot.core.ecc.pas.
We did not start to work on it yet. But it is something we will implement, since we need it for the future.
@wangming
What do you call "SpingCloud"?
I think this is Spring - a Java framework
]]>Delphi has been obsolete for a while, if anyone can name one thing that gives delphi advantage over FPC I would love to hear it. Delphi is a paid product and they only added linux support a few years ago and even then it's based on LLVM compiler chain so minimum effort there (I guess you have to do that when you fire your entire compiler team). I only use Delphi because of a legacy product I have to support and I don't have time right now to rewrite for FPC. I think this is the same for the very small community still using Delphi.
I totally agree with you about Delphi, but I was talking about Object Pascal in general.
I use Delphi 7 because of a legacy product too. New projects I use FPC/Lazarus.