ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tom.dieder...@gridgain.com
Subject Invitation: RSVP now for Dec. 13 Bay Area In-Memory Computing Meetup! @ Wed Dec 13, 2017 6pm - 8pm (CST) (dev@ignite.apache.org)
Date Mon, 20 Nov 2017 22:54:57 GMT
You have been invited to the following event.

Title: RSVP now for Dec. 13 Bay Area In-Memory Computing Meetup!
We have a great meetup planned for the evening of Dec. 13! In-memory  
computing experts from Hazelcast and GridGain Systems will be speaking.  
And, of course, we’ll have great food, drinks – and cool raffle prizes, too!

Please RSVP here so we can order the appropriate food and beverages.
http://bit.ly/2AgZdpb

Speakers:
Valentin (Val) Kulichenko, GridGain Systems
Fuad Malikov, Hazelcast

Talk one: (Hazelcast) Java SE 8 Stream API is a modern and functional API  
for processing Java Collections. Streams can do parallel processing by  
utilizing multi-core architecture, without writing a single line of  
multithreaded code. Hazelcast JET is a distributed, high-performance stream  
processing DAG engine, which provides distributed Java 8 Stream API  
implementation. This session will highlight this implementation of Stream  
API for big-data processing across many machines from the comfort of your  
Java Application.

With an explanation of internals of the implementation, I will give an  
introduction to the general design behind stream processing using DAG  
(directed acyclic graph) engines and how an actor-based implementation can  
provide in-memory performance while still leveraging industry-wide known  
frameworks as Java Streams API.


Talk two: (GridGain Systems) It’s well known that distributed systems rely  
very much on horizontal scalability. The more machines in your cluster -  
the better performance of your application, right? Well, not always. While  
a database can provide rich capabilities to achieve lightning fast  
performance, it’s an engineer's responsibility to use these capabilities  
properly as there are a lot of ways to mess things up.

During this meetup, Valentin Kulichenko, GridGain System’s Lead Architect,  
will talk about challenges and pitfalls one may face when architecting and  
developing a distributed system. Valentin will show how to take advantage  
of the affinity collocation concept that is one of the most powerful and  
usually undervalued technique provided by distributed systems. He will take  
Apache Ignite as a database for his experiments covering these moments in  
particular:

What is data affinity and why is it important for distributed systems? What  
is affinity colocation and how does it help to improve performance? How  
does affinity colocation affects execution of distributed computations and  
distributed SQL queries? And more…

After this talk, you will have better understanding about how distributed  
systems work under the hood, and will be able to better design your  
applications based on them.
When: Wed Dec 13, 2017 6pm – 8pm Central Time
Where: 1172 Castro St, Mountain View, CA 94040, USA
Calendar: dev@ignite.apache.org
Who:
     (Guest list has been hidden at organizer's request)

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=M2RrZ3Zxc2k5bGc1b3RxZTlwYzNtbzJxdm8gZGV2QGlnbml0ZS5hcGFjaGUub3Jn&tok=NjUjZ3JpZGdhaW4uY29tX2NpNG9xcm43YjlpYTRkcnRydXJxMDA0aWhzQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20zODQ1NjUwZDEyNDNiYTFlZDkzMDQwNzQ1MWYyZWUxYWRiYjZmMDRl&ctz=America/Chicago&hl=en

Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account dev@ignite.apache.org  
because you are an attendee of this event.

To stop receiving future updates for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP  
response. Learn more at  
https://support.google.com/calendar/answer/37135#forwarding
Mime
View raw message