Denis, thanks for the feedback! When should I publish the post? Right after official release announcement, or later?
> I would use "thick client" as a term instead of the "classic client" Good point, fixed > partition-awareness doesn't handle topology changes automatically (partition map won't be updated on the client-side) This is not true, we keep the partition map up to date by checking AffinityTopologyVersion [1] > Now I can run Ignite.NET easily on my Mac OS machine Just to clarify, you can do that since 2.4 release [2]. In 2.8 we have refined build-related things (jar file handling), and made sure that recent .NET versions are supported. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients [2] https://habr.com/ru/company/gridgain/blog/347374/ (in Russian) On Fri, Mar 6, 2020 at 2:40 AM Denis Magda <dma...@apache.org> wrote: > Pavel, thanks, > > I enjoyed reading the blog, crystal clear and straight to the point! Please > consider these several items that might strengthen the article a bit: > > - I would use "thick client" as a term instead of the "classic client" > (and mention that Ignite.NET client is a thick one). The thick client is > already a coined term that based on my observations are used a lot by > dev > and user communities. Also, you might add some differences of thick vs. > thin taking from this page - > > https://www.gridgain.com/docs/latest/installation-guide/deployment-modes#thick-vs-thin-clients > - Should we mention that presently partition-awareness doesn't handle > topology changes automatically (partition map won't be updated on the > client-side)? This might be a blocker for some users. > - Excited to read about the cross-platform support, that's huge! Now I > can run Ignite.NET easily on my Mac OS machine. I would insert a > reference > to updated documentation pages that explain how to start with > Ignite.NET on > various platforms. > > Hope, you will find this helpful, thanks for helping with project > promotion! > > - > Denis > > > On Thu, Mar 5, 2020 at 7:32 AM Pavel Tupitsyn <ptupit...@apache.org> > wrote: > > > Denis, > > > > The first post is going to be ready soon, probably by tomorrow. > > Here is a draft, feedback welcome: > > > > > https://github.com/ptupitsyn/ptupitsyn.github.io/blob/ignite-2.8/_posts/2020-03-05-Whats-New-In-Ignite-Net-2.8.md > > > > On Wed, Mar 4, 2020 at 5:15 PM Denis Magda <dma...@apache.org> wrote: > > > > > Hi Pavel, > > > > > > Excellent! It will be good to publish the first article (what's new in > > > Ignite.NET 2.8) prior to a generic blog on blogs.apache.org so that we > > can > > > link your post in for those who are looking for more details. Do you > have > > > any timeline in mind for this article? > > > > > > @Alexey Zinoviev <zaleslaw....@gmail.com>, how about you preparing > > several > > > paragraphs for the blog highlighting the biggest changes in ML? The > same > > > highlighted content will be elaborated during the webinar. > > > > > > - > > > Denis > > > > > > > > > On Wed, Mar 4, 2020 at 2:29 AM Pavel Tupitsyn <ptupit...@apache.org> > > > wrote: > > > > > > > Denis, I have a few blog posts on Ignite.NET planned: > > > > > > > > * What's new in Ignite.NET 2.8 (Thin Client Partition Awareness, > > logging, > > > > expiry policy, cluster API, .NET Core 3.x, Dockerfile) > > > > * Ignite.NET performance improvements on .NET Core 3.x > > > > * Ignite.NET Partition Awareness performance > > > > * Fixing JNI thread leak in Ignite.NET > > > > > > > > What do you think? Should we have a schedule of some sorts? > > > > > > > > On Tue, Mar 3, 2020 at 9:58 PM Alexey Zinoviev < > zaleslaw....@gmail.com > > > > > > > wrote: > > > > > > > > > Sounds ineresting, will help with the post, please share the > > template, > > > > not > > > > > sure about webinar > > > > > > > > > > вт, 3 мар. 2020 г., 20:59 Denis Magda <dma...@apache.org>: > > > > > > > > > > > Igniters, > > > > > > > > > > > > Let's discuss approaches for a global announcement/promotion of > the > > > > > > release. I would suggest focusing on a blog post and a community > > > > webinar. > > > > > > > > > > > > The blog post will introduce significant improvements (service > > grid, > > > > thin > > > > > > clients, new metrics system, ML, etc.) sharing references to > > > > > documentation > > > > > > pages with more details. It will be published on > blogs.apache.org > > > in > > > > a > > > > > > format similar to this one - > > > > > > https://blogs.apache.org/ignite/entry/apache-ignite-2-7-deep. I > > can > > > > work > > > > > > on > > > > > > it unless anybody else is willing to share the news on behalf of > > the > > > > > > community. > > > > > > > > > > > > Next, the blog post will be featuring a community webinar that is > > > > > breaking > > > > > > down a subset of the improvements in more detail. Please see an > > > > abstract > > > > > > below with suggested topics for a detailed overview. @Alexey > > Zinoviev > > > > > > <zaleslaw....@gmail.com>, would you be able to present the ML > > part? > > > > > > @Nikolay > > > > > > Izhikov <nizhi...@apache.org> or @Andrey Gura < > ag...@gridgain.com> > > > > would > > > > > > you like to take over the metrics section? I'll work the > attendees > > > > > through > > > > > > the items listed in "Sustainable production under high load". We > > > should > > > > > > target the webinar for the April timeframe. > > > > > > > > > > > > > > > > > > > > > > > > *Topmost changes in Apache Ignite 2.8 for production maintenance > > and > > > > > > machine learning* > > > > > > > > > > > > > > > > > > *Apache Ignite community rolled out more than 1900 changes in > > Ignite > > > > 2.8 > > > > > > that enhanced almost all the components of the platform. The > > release > > > > > notes > > > > > > go with hundreds of lines trying to catalog the improvements. > Join > > > this > > > > > > webinar led by Ignite community members demonstrating and > > dissecting > > > > new > > > > > > capabilities related to production maintenance, monitoring, and > > > machine > > > > > > learning that you do not want to lose sight of:* > > > > > > > > > > > > - *Sustainable production under high load: Ignite persistence > > > > > compaction > > > > > > and consistent crash recovery, baseline topology > > auto-adjustment, > > > no > > > > > > interruption of operations for some cluster topology change > > > events.* > > > > > > - *Next-generation system for monitoring and code tracing: > > design > > > > and > > > > > > usage, exporters configuration (JMX, SQL, OpenCensus) * > > > > > > - *Ignite Machine Learning major upgrade: a revised approach > for > > > > > models > > > > > > training/evaluation, models importing from Spark ML, XGBoost > and > > > > much > > > > > > more > > > > > > * > > > > > > > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > > > > > > > > > >
