Happy Friday everyone 👋! The Data Platform team is traditionally here with the updates.

Our main focus this week was on improving the NEAR Lake Framework and empowering users with an additional data pipeline about account activity.

Also, this week the recording of the Data Platform Community Meeting was published on YouTube. By the way, according to the survey we've made during the call the most votes were saying the community wants to have the NEAR Lake Framework Python version. We're taking it into account 😉

This week the Data Platform team:

Hey everyone! As you remember a few weeks ago a Data Platform Community Meeting had happened. Finally, we've published a record from the meeting to YouTube

We was talking about:

• the team's goals for this quoter
• the history of Indexers in NEAR Protocol
• the Data in NEAR Protocol, who is relying on it, what challenges we are facing with, what are we going to do

Enjoy the video, feel free to ask questions in the comments under the video, leave a feedback about the Community Meeting and maybe what do you want us to speak about next time.

The video is under the cut, click Read More

👋 Greeting! We are from the Data Platform team, and we're here for you with the weekly updates!

This week the team was focused on finalizing the JavaScript version of NEAR Lake Framework and on the NEAR Lake Flow into SQL Base.

Now having the NEAR Lake ecosystem in place we're thinking about coming back to the Indexer as a Service idea described on NEAR Gov Forum almost a year ago.

Stuff we've managed to do this week:

👋 Hey hey hey! The Data Platform team is here! We've brought the traditional portion of weekly updates.

We believe this week had a historical meaning: the first Data Platform community meeting had happened. It was a pleasure to see all of you! (Follow the NEAR YouTube channel if you missed the meeting, the record will be published soon).

Let's get to updates:

👋 Greetings from the Data Platform team! We're here to share our updates for the week. While this week was as quick as the previous one for us, we've managed to bring you some news.

🎉 Please welcome to the new place where indexers-related docs live https://near-indexers.io/

This week we were focusing on:

👋 Wow, that was a very quick week. Hello everyone! Data Platform Team is here for the weekly updates. Unfortunately didn't succeed in publishing the Indexer Docs this week, because we're dealing with dedicated domain stuff. I really hope we'll do it next week.

Our team has created a draft OKRs for the 2022 Q2 and soon enough it will be finalized, so we've defined our focus for the next quarter 🎉

Our main focus remains the same:

👋 Greetings! Data Platform Team is here with the updates. Don't have much to say, especially in comparison with the previous exciting week 😅. We are mostly focused on rewriting the Indexer for Explorer. Meanwhile, we are working on the creation of a whole new space with indexer docs, we want to create a knowledge base to share with everyone to help understand what indexer is, how to create one, and find out whether you need it in the first place.

Some details:

👋👋 Hello-hello everybody! The Data Platform Team is here with the updates. It's been a wild week with big news, you know.

We invite early adopters to use the brand-new way of building indexers. If you run an indexer already, please consider migrating to NEAR Lake Framework. This will drastically decrease your spending on infrastructure and eventually will minimize the time you need to maintain your indexers.

So, since the previous week:

👋 Hello everyone! It's been a while since the last update. Things went bananas in the world. Data Platform Team is currently safe and continues working. We're pushing the MVP release of NEAR Lake project and working on the refactoring of NEAR Indexer for Explorer. We're changing the data storage for Indexer for Explorer from PostgreSQL to SingleStore, it should improve the stability of the data flow and it should end up improving the stability of NEAR Explorer. At least in terms of data availability and decreasing the possible interruptions.

Since the previous update:

👋 How's it going, everyone? Seems like we are renaming to Data Team 🤷, so Data Team is here with fresh weekly updates. All the week we were working on NEAR Lake pushing it to MVP release as hard as we could.

Since the previous week: