Ed, This proposed talk is nice with a line up of honest and individual contributors.
Community, would you like to contribute to an open doc on assessment b/W Fineract 1.x and proposed architecture of CN for a deeper review. https://docs.google.com/document/d/1-mrwaDosVLisRrbfUXT7Oy8sTWzOIXBoRekmpg8ujI0/edit Aleksandar, would you also add your suggestions in the same doc. By the way, we implemented modularity in Fineract 1.x last year itself. Thanks everyone. Let’s not reinvent the wheel! Let’s move forward. On Tue, 14 Sep 2021 at 09.12, Aleksandar Vidakovic < [email protected]> wrote: > Hi James, > > ... I can soon (tomorrow?) share my presentation on Fineract 1.x > modularity suggestions, maybe there's one or the other thing interesting > for you... contains also some information about - major - performance and > reliability improvements done in collaboration with Fiter.io. In a nutshell: > > - we replaced the command processing mechanics with Apache Camel > - put RabbitMQ in place for reliability (RabbitMQ can be replaced with > pretty much any other queue system supported by Camel like Kafka, JMS, SQS > etc. with only a few lines of configuration) > - added client websocket connections for truly > asynchronous processing/result delivery > - ... all while keeping the REST API 99% backwards compatible (clients > only have to add the websocket back-channel to receive results; existing > implementations - e. g. Fineract Java client - won't break) > > FYI > > Cheers, > > Aleks > > On Tue, Sep 14, 2021 at 6:47 AM Prashant Rahulkar < > [email protected]> wrote: > >> Hello James, >> >> >> >> My company interested to manage the product like Share Certificate of the >> small micro-finance; >> >> The yearly declared dividend should be managed, transfer, withdrawal the >> amount should be manage. >> >> >> >> Thanks & Regards, >> >> Prashant Rahulkar | CEO >> >> Mobile : +91 98505 75226 >> >> Address : 603, Akshay, Phase-2, Pune-411027 >> >> [image: Description: Equation-New] >> >> WebSite : www.riequation.com >> >> >> >> >> >> >> >> >> >> >> >> >> >> *From:* James Dailey [mailto:[email protected]] >> *Sent:* Tuesday, September 14, 2021 9:22 AM >> *To:* Dev >> *Subject:* State of the Project >> >> >> >> Devs - I will, shortly, be posting the results of the survey that we took >> in late August. A bit delayed. >> >> >> >> I wanted to share that I am going to be giving a "State of the Project" >> talk at ApacheCON next week and I would like your input into that. >> ApacheCON is the annual conference that this year is again online. >> https://www.apachecon.com/acah2021/tracks/. Register today! >> >> >> >> To help me with my REPORT OUT: Please feel free to share observations, >> criticisms, concerns, as well as compliments to specific contributors. >> Please either respond on list, or email me directly. >> >> >> >> If you or your company is engaged in developing new features and wants to >> be mentioned, I would like to highlight that. >> >> >> >> There is much to celebrate and I am very grateful to all of the >> contributors this past year. >> >> >> >> Thank you, >> >> - James >> > -- Ankit Managing Partner Muellners Inc 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.
