According to our work if you look at
https://github.com/muellners/finscale-accounting , is a migration from
CN services but with less efforts , according to our study we took
about a week to finish the migration from CN , and now imagine if
someone wants to build a new service how fast it can be.
Pointing to the other direction , this can lead to divergence from
fineract CN , since it replaces the idea of less fineract based
dependency by offloading it to just 2 Axon and Jhipster , your
question might be why this? I don't have an answer now.
You could say: Hey maybe rather than changing all of this , you
should just bring changes to the existing work, but existing work
requires more effort to change.
I invite folks from the community to try out the work themselves , and
let experience speak , since many have joined already in this course
of development and are liking the way this method is used.
We are bringing back the microservice pattern back to fineract CN
Thanks
On Wed, Aug 26, 2020 at 11:33 AM Saransh Sharma <[email protected]
<mailto:[email protected]>> wrote:
With most of the projects showing negligible or no activity at all
for about an year, the fineract-cn project looks so close to being
looked upon as an abandoned beast. And because the difficulties
one has to go through to tame this beast, not many people get to
enjoy the real beauty it really is. With our work, we hope to make
a difference to this current state of the project and to attract
more people into getting to know the project and make
contributions by making it easier for them so that we can steer
the project towards a more mature, stable, complete and releasable
version.
Currently, the fineract-cn project is no different from its
predecessor when it comes to upgradation. The projects were not
actively upgraded to latest versions of spring boot incrementally,
and so it becomes a bit harder to maintain over time, is not able
to reap the benefits of newer versions of Spring Boot and this
also increases learning curve for newcomers because most of them
come in just after learning technology which is relevant when
they’re trying to make an entry. We’re planning to tackle this by
migrating the fineract-cn group of projects over to a Jhipter
base. By doing this, even if minor incremental upgrades are not
done, someone could carry out an upgradation process just by
following the Jhipter upgrade process. The Jhipster ecosystem is
actively under development and improved and so, by being able to
follow them means being able to stay relevant in terms of
technology stack rather than just being able to upgrade Spring
Boot itself. By migrating over to Jhipster, we also aim to make it
easier for someone who’s interested in improving fineract-cn –
it’d be as easy as generating a new jhipster project and
registering it with Jhipster registry(It is a Eureka server which
also packs a spring cloud config server and many other features),
with as less fineract-cn’ish stuff to be injected into the
project. We have come up with a Jhipster blueprint to do these
injections for the developers. We have got rid of cassandra in
favour of message oriented architecture using Axon because
cassandra becomes a point of suffering for someone who’s trying to
deploy fineract-cn on a production scale because maintaining a
cassandra cluster is a very complex task on its own and will soon
turn out to be an expensive option on the infrastructural
side(Then its no longer a project where MFIS can use). On top of
all these we’re also making some improvements in the architecture
of fineract-cn, by introducing more flexibility in the ability for
a service to register and use a specific database other than
Postgres, which is currently being used. For example, if a service
decides to use Neo4J and not use postgres at all, it can very well
go ahead and do this. This is currently a point where developers
are being restricted. We’re not saying that every service needs to
use a different database, which would soon grow to be
unmanageable, but to give it a room for flexibility when there is
a need.
Eventually we can decide which version to go with if this a fork
then be it.
Thanks
On Wed, Aug 26, 2020 at 10:35 AM James Dailey
<[email protected] <mailto:[email protected]>> wrote:
Hi Saransh -
It's generally a good idea to:
A) bring ideas to the community for consideration, &&
B) to have the approach that builds on what the community is
already investing time in doing, or...
C) to argue in a cogent way, how your approach, whilst a
departure from the existing, is better.
These A,B,C's seem normative.
So, speaking as a member of this group, I'm trying to
understand: what you are proposing?
Is this a significant revamp of the fineract-CN microservices
architecture?
Is this proposal coming from you as a potential contribution
to fineract-CN?
Are you proposing a new fineract project compliant w Apache
licenses?
Is this marketing of company services for implementation of
fineract in a particular way? Or a code fork ?
Could you please clarify onlist?
Thanks.
On Tue, Aug 25, 2020, 9:33 PM Saransh Sharma
<[email protected] <mailto:[email protected]>> wrote:
Usually any open source project , typically should have
multiple implementations (in case of Linux or Bitcoin) now
it's up to the user which version they wish to use. We are
proposing this new architecture in the coming Apache con,
before that we would like to share our progress with
Community before we actually reveal all the details.
Some steps now in the future involves like
1. Dry test of the functional feature , we have recently
finished accounting migration
2. Identity and consumer service with deposit account
management test run.
In my opinion, @Awasum Yannick
<mailto:[email protected]> should join the discussion too.
On Wed, Aug 26, 2020 at 6:27 AM Michael Vorburger
<[email protected] <mailto:[email protected]>> wrote:
I'm not entirely sure what this thread is about.
If this discusses a new project ("Finscale" ?) hosted
on https://github.com/muellners/, then I must join
Awasum in expressing reservations about a non Apache
project being discussed on the [email protected]
<mailto:[email protected]> mailing list.
If this is a discussion about possible future
architectural evolution of the Apache Fineract CN
project (despite the linked GDoc stating "Fineract CN
is history and is slowly moving towards extinction."
?), then I guess it's fine.
On Fri, Aug 21, 2020 at 6:58 PM Saransh Sharma
<[email protected] <mailto:[email protected]>>
wrote:
Here is the meeting recording for folks who wish
to watch the event.
https://drive.google.com/file/d/1atM7mG4Nec2fNd9alDWrsOt9Mqqt-FEZ/view?usp=sharing
On Fri, Aug 21, 2020 at 4:06 PM Saransh Sharma
<[email protected]
<mailto:[email protected]>> wrote:
Here is the meeting link feel free to join.
https://meet.google.com/koa-thmo-abq?authuser=0
On Fri, Aug 21, 2020 at 3:43 PM Saransh Sharma
<[email protected]
<mailto:[email protected]>> wrote:
Anyone willing to join let me know now, i
will add them to the RSVP list.
Thanks
On Fri, Aug 21, 2020 at 2:53 PM Ankit
Muellner <[email protected]
<mailto:[email protected]>> wrote:
@Awasum,
I think the relevant Gdoc is a work in
progress discussion document
(something like a pre meeting note or
objective discussion notes) not a
technical wiki document. (This means
such a document does not require any
open source character.)
There is an OSS usage and delivery
policy here
<https://docs.muellners.info/open-source-policies/open-source-usage-and-delivery-policies>
regarding
this branched project's development,
consistent with Apache Fineract project.
We must remember that the current
documentation of Fineract requires
revamp(as is true for any
documentation standards) and we should
not further make these writeups more
complicated by adding anything non
substantial(e.g this Gdoc). This is
one suggestion I have for the current
PMC team and specifically You.
We must avoid creating a heavy non
sequential wiki. I understand we have
a Lazy consensus in place but for
certain key objectives e.g Fineract CN
upgrade, broader modules etc, this
community requires a Workflow for
addition of write ups to its wiki.
You are right once the associated
documentation for this thread reaches
maturity, we i.e Muellners should be
adding them to Fineract wiki just
like everyone else i.e
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
Hope this clarifies.
On Fri, Aug 21, 2020 at 10:48 AM
Awasum Yannick
<[email protected]
<mailto:[email protected]>> wrote:
Hi Saransh,
On Fri, Aug 21, 2020 at 6:40 AM
Saransh Sharma
<[email protected]
<mailto:[email protected]>> wrote:
Hey , Devs and Partners
We are back with more updates
and planning to host yet
another session of Fineract CN
Updates
1. Last time we discussed
product upgrade documentation
(Which is in place
https://docs.google.com/document/d/1TQox0fQvQexMFj2gX6Si74osKrT5mcIGoYd-mWp3hrc/edit#)
This GDoc is not openly available
to everyone. Is this private to
your company or is it for the
Fineract Open Source Community? If
we need to request for access
before viewing the doc then that
is not really Open Source.
Will you be comfortable sharing
your notes on Fineract Wiki:
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home
What libraries have you all
upgraded? And have you sent PRs on
our Apache Fineract CN repos? Or
is this something completely
private or code Open Sourced under
your company Org?
2. Migrating services quicker
then before (We might give
some walkthrough)
3. We would be focusing on
today's call : Migration from
Fineract 1.x to CN where we
use the existing functional
feature in CN.
Is there a repo for the above? Or
a PR already opened on Fineract
repos? Or is this just an idea?
4. Developer Perspectives
5. Deployment Scenario
Thanks here is the calendar
invite join in and lets spread
work.
https://calendar.google.com/event?action=TEMPLATE&tmeid=M2Yzb3FjZ3ViazhzYWg3NnFxMzVvM2dhbjEgc2FyYW5zaEBtdWVsbG5lcnMub3Jn&tmsrc=saransh%40muellners.org
I wonder if we can use the
Fineract Wiki available here:
https://cwiki.apache.org/confluence/display/FINERACT/Fineract+Home to
document the work we are doing. It
will have the docs all in one
place and not scattered all around.
It will be great if you can record
your calls and share with the rest
of the community who can't attend
these calls. This makes it easy
for people to catch up.
Thanks.
Awasum
--
Ankit Müllner
Muellners Europe
+4581929792
This mail is governed by Muellners®
IT policy.
The information contained in this
e-mail and any accompanying documents
may contain information that is
confidential or otherwise protected
from disclosure. If you are not the
intended recipient of this message, or
if this message has been addressed to
you in error, please immediately alert
the sender by reply e-mail and then
delete this message, including any
attachments. Any dissemination,
distribution or other use of the
contents of this message by anyone
other than the intended recipient is
strictly prohibited. All messages sent
to and from this e-mail address may be
monitored as permitted by applicable
law and regulations to ensure
compliance with our internal policies
and to protect our business. E-mails
are not secure and cannot be
guaranteed to be error free as they
can be intercepted, amended, lost or
destroyed, or contain viruses. You are
deemed to have accepted these risks if
you communicate with us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT
policy.
The information contained in this e-mail
and any accompanying documents may contain
information that is confidential or
otherwise protected from disclosure. If
you are not the intended recipient of this
message, or if this message has been
addressed to you in error, please
immediately alert the sender by reply
e-mail and then delete this message,
including any attachments. Any
dissemination, distribution or other use
of the contents of this message by anyone
other than the intended recipient is
strictly prohibited. All messages sent to
and from this e-mail address may be
monitored as permitted by applicable law
and regulations to ensure compliance with
our internal policies and to protect our
business. E-mails are not secure and
cannot be guaranteed to be error free as
they can be intercepted, amended, lost or
destroyed, or contain viruses. You are
deemed to have accepted these risks if you
communicate with us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT policy.
The information contained in this e-mail and
any accompanying documents may contain
information that is confidential or otherwise
protected from disclosure. If you are not the
intended recipient of this message, or if this
message has been addressed to you in error,
please immediately alert the sender by reply
e-mail and then delete this message, including
any attachments. Any dissemination,
distribution or other use of the contents of
this message by anyone other than the intended
recipient is strictly prohibited. All messages
sent to and from this e-mail address may be
monitored as permitted by applicable law and
regulations to ensure compliance with our
internal policies and to protect our business.
E-mails are not secure and cannot be
guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have
accepted these risks if you communicate with
us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT policy.
The information contained in this e-mail and any
accompanying documents may contain information
that is confidential or otherwise protected from
disclosure. If you are not the intended recipient
of this message, or if this message has been
addressed to you in error, please immediately
alert the sender by reply e-mail and then delete
this message, including any attachments. Any
dissemination, distribution or other use of the
contents of this message by anyone other than the
intended recipient is strictly prohibited. All
messages sent to and from this e-mail address may
be monitored as permitted by applicable law and
regulations to ensure compliance with our internal
policies and to protect our business. E-mails are
not secure and cannot be guaranteed to be error
free as they can be intercepted, amended, lost or
destroyed, or contain viruses. You are deemed to
have accepted these risks if you communicate with
us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT policy.
The information contained in this e-mail and any
accompanying documents may contain information that is
confidential or otherwise protected from disclosure. If
you are not the intended recipient of this message, or if
this message has been addressed to you in error, please
immediately alert the sender by reply e-mail and then
delete this message, including any attachments. Any
dissemination, distribution or other use of the contents
of this message by anyone other than the intended
recipient is strictly prohibited. All messages sent to and
from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with
our internal policies and to protect our business. E-mails
are not secure and cannot be guaranteed to be error free
as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these
risks if you communicate with us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT policy.
The information contained in this e-mail and any accompanying
documents may contain information that is confidential or
otherwise protected from disclosure. If you are not the intended
recipient of this message, or if this message has been addressed
to you in error, please immediately alert the sender by reply
e-mail and then delete this message, including any attachments.
Any dissemination, distribution or other use of the contents of
this message by anyone other than the intended recipient is
strictly prohibited. All messages sent to and from this e-mail
address may be monitored as permitted by applicable law and
regulations to ensure compliance with our internal policies and to
protect our business. E-mails are not secure and cannot be
guaranteed to be error free as they can be intercepted, amended,
lost or destroyed, or contain viruses. You are deemed to have
accepted these risks if you communicate with us by e-mail.
--
Thanks and regards,
Saransh Sharma
Research Partner
This mail is governed by Muellners® IT policy.
The information contained in this e-mail and any accompanying
documents may contain information that is confidential or otherwise
protected from disclosure. If you are not the intended recipient of
this message, or if this message has been addressed to you in error,
please immediately alert the sender by reply e-mail and then delete
this message, including any attachments. Any dissemination,
distribution or other use of the contents of this message by anyone
other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal
policies and to protect our business. E-mails are not secure and
cannot be guaranteed to be error free as they can be intercepted,
amended, lost or destroyed, or contain viruses. You are deemed to have
accepted these risks if you communicate with us by e-mail.
