Why is #WorldEmojiDay on 17th July?
| Blog | https://underthehood.meltwater.com |
| https://twitter.com/MeltwaterEng | |
| https://instagram.com/MeltwaterEngineering | |
| YouTube | https://youtube.com/@MeltwaterEng |
Meltwater Engineering
@MeltwaterEng@techhub.social
- 9 Followers
- 7 Following
- 15 Posts
Stories from the Meltwater Product & Engineering team. We talk about the work we do, tech, doing good, and other things we are passionate about.
🤔 Do you prefer to sit or stand at your desk?
Sit
Stand
Mixture of both
Poll ended at .
We're hiring! We are looking for ambitious professionals in the US 🇺🇸 who would like to grow with our Application Support team. See our full job listing and salary range: https://emp.jobylon.com/jobs/168414-meltwater-product-engineering-product-support-engineer
#ProductSupportEngineer #ApplicationSupport #JobOpening #Hiring https://t.co/QXRJeY9LNY
Product Support Engineer | Meltwater Product & Engineering
Do you want to work in a dynamic global organization, solving interesting, real time problems for customers? We are looking for ambitious professionals who would like to grow with our Application Support team. The role involves monitoring and diagnosing application and system problems, or issues that are disrupting the application service platform that business users depend on. Crucially, applications are in production, or live, and issues need immediate attention with early diagnosis and response. Responsibilities: Work within a dynamic, international team to support customers throughout the world Manage, prioritize, and troubleshoot a pipeline of tickets, application requests, and project activities Respond to system generated alerts and/or escalations relating to any failures on the service platform Work with Engineering teams to determine root cause of problems and deliver effective solutions Work on projects focused on continuous improvement of the application support model and associated processes Document standards, processes, and procedures relating to best practices, issues, and resolutions The hours for this position will be 10:00 AM EST - 7:00 PM EST. There may be occasional domestic and/or international travel for team meetings Compensation: Competitive salary $65,000 - $75,000 USD annually Health Coverage (Dental, Medical, Vision, for both you and dependents) Flex Spending Accounts (Child Care, Commuter, Health) Life Insurance Retirement Savings and Employer Matching Paid Parental Leave Competitive PTO/Holiday Plan Ongoing Training and Professional Development
What are you listening to while coding? 🤔
The final part of our 3#petabyte #Elasticsearch cluster upgrade series is out.
We discuss the benefits of the upgrade and provide more details on our new architecture.
If you work with Elastic and #bigdata, there's lots to learn in this post.
How we upgraded an old, 3PB large, Elasticsearch cluster without downtime. Part 7 - Final Architecture & Learnings
This is the 7th and final part of our blog post series on how we upgraded our Elasticsearch cluster without downtime and with minimal user impact. In this post, we will focus on several of the benefits we have seen after the upgrade and provide more details on how our architecture looks today.
Our engineering blog, Underthehood, is 10 years old! 🎂
The Underthehood archive has every single blog post we've published
https://underthehood.meltwater.com/
We're over half way through our blog series on upgrading out 4PB #elasticsearch cluster! This post is about how we supported two Elasticsearch clients in the same JVM.
Check the post out and the rest of the series too! https://underthehood.meltwater.com/blog/2022/12/09/how-we-upgraded-an-old-3pb-large-elasticsearch-cluster-without-downtime-part-5-running-two-elasticsearch-clients-in-the-same-jvm/
How we upgraded an old, 3PB large, Elasticsearch cluster without downtime. Part 5 - Running two Elasticsearch clients in the same JVM
This is part 5 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. Due to the large scope of this upgrade, it was clear from the beginning that this project was going to last for at least one year, if not more. This blog post describes how we reasoned about our development process and how we managed to support multiple Elasticsearch client libraries in our Java code bases for a long time.
It's time for the 4th in our blog post series about upgrading our 3PB Elastic #elasticsearch cluster without downtime. Part 4 is about #tokenization to ensure have high recall for over 240 🗺️ languages we support in our platform.
How we upgraded an old, 3PB large, Elasticsearch cluster without downtime. Part 4 - Tokenization and normalization for high recall in all languages
This is part 4 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. In part 2 we explained that we decided to do a full reindexing of our entire dataset as part of this Elasticsearch upgrade project. This blog post explains some of the changes we made to our documents during that re-indexing.
We've published part 3 of our "3 Petabyte Elastic upgrade without downtime" series! This week it's all about search performance and wildcards.
This blog post also introduces Johan, our third different author in the series!
How we upgraded an old, 3PB large, Elasticsearch cluster without downtime. Part 3 - Search Performance & Wildcards
This is part 3 in our series on how we upgraded our Elasticsearch cluster without any downtime and with minimal user impact. As part of the Elasticsearch Upgrade project, we needed to investigate the search performance improvements between the old and the new versions. Running an older version of Elasticsearch has presented many performance issues over the years and we hoped that upgrading to a more recent version would help. This blog post will describe how we tested the search performance of our new Elasticsearch cluster and the different optimizations we used to improve it. Specifically, we will focus on how we solved the major bottleneck for our use case: wildcards.
Last Friday, on Twitch, we had @OllieParsley streaming his hackathon project. Here is the replay: https://www.youtube.com/watch?v=hwQ5aK9kzXc
The project was done in Go and took tweets from https://twitter.com/MeltwaterEng and forward them to this Mastodon account in real-time.
