A Guide to Freeing Yourself from Legacy RDBMS

Oracle introduced the first commercial relational database (RDBMS) to the market in 1979 — more than a decade before the World Wide Web. Now, digital transformation is reshaping every industry at an accelerating pace. In an increasingly digital economy, this means a company's competitive advantage is defined by how well they build software around their most critical asset — data. MongoDB and Palisade Compliance have helped some of the largest and most complex Oracle customers transform their architecture and shift to a cloud-first world. Although every client is unique, we have identified three important steps to moving away from Oracle software, reducing costs, and achieving their digital transformation goals: Understand your business and technical requirements for today and tomorrow, and identify the technical solution and company that will be by your side to help future-proof your organization. Decipher your Oracle contracts and compliance positions to maximize cost reduction initiatives and minimize any risks from Oracle audits and non-compliance that may derail your ultimate goals. Mobilize internal momentum and traction to make the move. MongoDB can help with #1, Palisade Compliance assists with #2, and you have to supply #3. This is a guide to getting started, as outlined by the main pillars of success above. 1. Understand your requirements and find the right partner — MongoDB The most common requirements we hear from organizations are that they need to move faster, increase developer productivity, and improve application performance and scale -- all while reducing cost and breaking free from vendor lock-in. For example , to keep pace with demands from the business, Travelers Insurance modernized its development processes with a microservices architecture supported by agile and DevOps methodologies. But the rigidity of its existing Oracle and SQL Server databases created blockers to move at the speed they needed. The solution was MongoDB and its flexible data model. They eliminated the three-day wait to make any database changes, creating a software development pipeline supporting continuous delivery of new business functionality. Similarly, Telefonica migrated its customer personalization service from Oracle to MongoDB. Using Oracle, it took 7 developers, multiple iterations and 14 months to build a system that just didn't perform. Using MongoDB, a team of 3 developers built its new personalization service in 3 months, which now powers both legacy and new products across the globe. MongoDB helps Telefonica be more agile, save money and drive new revenue streams. While some organizations try to innovate by allowing siloed, modern databases to coexist with their legacy relational systems, many organizations are moving to fully replace RDBMS. Otherwise, a level of complexity remains that creates significant additional work for developers because separate databases are required for search, additional technologies are needed for local data storage on mobile devices, and data often needs to be moved to dedicated analytics systems. As a result, development teams move slowly, create fewer new features, and cost the organization more capital. MongoDB provides the industry’s first application data platform that allows you to accelerate and simplify how you build with data for any application. Developers love working with MongoDB’s document model because it aligns with how they think and code. The summarized functional requirements that we typically hear from leading companies and development teams regarding what they require from a data platform include: A data structure that is both natural and flexible for developers to work with Auto-scaling and multi-node replication Distributed multi-document transactions that are fully ACID compliant Fully integrated full-text search that eliminates the need for separate search engines Flexible local datastore with seamless edge to cloud sync In-place, real-time analytics with workload isolation and native data visualization Ability to run federated queries across your operational/transactional databases and cloud object storage Turnkey global data distribution for data sovereignty and fast access to Data Lake Industry-leading data privacy controls with client-side, field level encryption Freedom to run anywhere, including the major clouds across many regions MongoDB delivers everything you need from a modern data platform. But it’s not just about being the right data platform; we’re also the right modernization partner. Through our Modernization Program we have built and perfected modernization guides that help you select and prioritize applications, review best practices, and design best-in-class, production-grade, migration frameworks. We’ve built an ecosystem around accelerating and simplifying your journey that includes: deployment on the leading cloud providers to enable the latest innovations technology companies that help with data modeling, migration, and machine learning, and expert System Integrators to provide you with tools, processes and support to accelerate your projects. We are proud to be empowering development teams to create faster and develop new features and capabilities, all with a lower total cost of ownership. 2. Manage Oracle as you move away — Palisade Compliance Oracle’s restrictive contracts, unclear licensing rules, and the threat of an audit can severely impact a company’s ability to transform and adopt new technologies that are required in a cloud-first world. To move away from Oracle and adopt new solutions, companies must be sure they can actually reduce their costs while staying in compliance and avoiding the risks associated with an audit. There will be a time when you are running your new solution and your legacy Oracle software at the same time. This is a critical phase in your digital transformation as you do not want to be tripped up by Oracle’s tactics and forced to stay with them. It may seem counterintuitive, but as you spend less with Oracle you must be even more careful with your licensing. As long as you keep spending money with Oracle and renewing those expensive contracts, the threat of an audit and non-compliance will remain low. Oracle is unlikely to audit a company that keeps giving it money. However, the moment you begin to move to newer technologies, your risk of an audit significantly increases. As a result, you must be especially vigilant to prevent Oracle from punishing you as you move away from them. Even if you’ve found a technical partner and managed your Oracle licenses and compliance to ensure no surprises, you still have to find a way to reduce your costs. It’s not as simple as terminating Oracle licenses and seeing your support costs go down. As stated above, Oracle contracts are designed to lock in customers and make it nearly impossible to actually reduce costs. Palisade Compliance has identified eleven ways to manage your Oracle licenses and reduce your Oracle support. It is critical that you understand and identify the options that work for your firm, and then build and execute on a plan that ensures your success. 3. Mobilize internal momentum and traction to make the move Legacy technology companies excel at seeding doubt into organization and preventing moves that threaten their antiquated solutions. Unfortunately, too many companies succumb to these tactics and are paralyzed into a competitive disadvantage in the market. In software, as in life, it’s easier to stay the course than to follow through with change. But when it comes to technical and business decisions that impact the overall success and direction of an organization, innovation and change aren’t just helpful, they’re necessary to survive--especially in a world with high customer demands and easy market entry. Ensuring you have the right technical partner and Oracle advisor is the best way to build the confidence and momentum needed to make your move. Creating that momentum is easier with MongoDB’s Database Platform, consisting of a fully managed service across 80+ regions, and Palisade’s expertise in Oracle licensing and contracts. Technical Alternative (MongoDB) + Independent Oracle Advisors (Palisade) ⇒ Momentum Parting thoughts To schedule a preliminary health check review and begin building the right strategy for your needs, fill out your information here . And to learn more about MongoDB’s Modernization Program, visit this page . About Palisade Compliance With over 400 clients in 30 countries around the world, Palisade is the leading provider of Oracle-independent licensing, contracting, and cost reduction services. Visit the website to learn more. To schedule a complementary one-hour Oracle consultation send an email to

Highlight What Matters with the MongoDB Charts SDK

We're proud to announce that with the latest release of the MongoDB Charts SDK you can now apply highlights to your charts. These allow you to emphasize and deemphasize your charts with our MongoDB query operators . Build a richer interactive experience for your customers by highlighting with the MongoDB Charts embedding SDK . By default, MongoDB Charts allows for emphasizing parts of your charts by series when you click within a legend. With the new highlight capability in the Charts Embedding SDK, we put you in control of when this highlighting should occur, and what it applies to. Why would you want to apply highlights? Highlighting opens up the opportunity for new experiences for your users. The two main reasons why you may want to highlight are: To show user interactions: We use this in the click handler sandbox to make it obvious what the user has clicked on. You could also use this to show documents affected by a query for a control panel. Attract the user’s attention: If there's a part of the chart you want your users to focus on, such as the profit for the current quarter or the table rows of unfilled orders. Getting started With the release of the Embedding SDK , we've added the setHighlight method to the chart object, which uses MQL queries to decide what gets highlighted. This lets you attract attention to marks in a bar chart, lines in a line chart, or rows in a table. Most of our chart types are already supported, and more will be supported as time goes on. If you want to dive into the deep end, we've added a new highlighting example and updated the click event examples to use the new highlighting API: Highlighting sandbox Click events sandbox Click events with filtering sandbox The anatomy of a click In MongoDB Charts, each click produces a wealth of information that you can then use in your applications , as seen below: In particular, we generate an MQL expression that you can use called selectionFilter , which represents the mark selected. Note that this filter uses the field names in your documents, not the channel names. Before, you could use this to filter your charts with setFilter , but now you can use the same filter to apply emphasis to your charts. All this requires is calling setHighlight on your chart with the selectionFilter query that you get from the click event, as seen in this sandbox . Applying more complex highlights Since we accept a subset of the MQL language for highlighting, it's possible to specify highlights which target multiple marks, as well as multiple conditions. We can use expressions like $lt and $gte to define ranges which we want to highlight. And since we support the logical operators as well, you can even use $and / $or . All the Comparison , Logical and Element query operators are supported, so give it a spin! Conclusion This ability to highlight data will make your charts more interactive and help you better emphasize the most important information in your charts. Check out the embedding SDK to start highlighting today! New to Charts? You can start now for free by signing up for MongoDB Atlas , deploying a free tier cluster and activating Charts. Have an idea on how we can make MongoDB Charts better? Feel free to leave an idea at the MongoDB Feedback Engine .

MongoDB Atlas as a Data Source for Amazon Managed Grafana

Amazon Managed Grafana is a fully managed service that is based on open source Grafana. Amazon Managed Grafana makes it easy to visualize and analyze operational data at scale. With Amazon Managed Grafana, organizations can analyze data stored in MongoDB Atlas without having to provision servers, configure or update software, or do the heavy lifting involved in securing and scaling Grafana in production. Connecting MongoDB Atlas to AMG The MongoDB Grafana plug-in makes it easy to query MongoDB with Amazon Managed Grafana. Simply select MongoDB as a data source, then connect to theMongoDB cluster using an Atlas connection string and proper authentication credentials (see Figure 1). Figure 1. Set up: MongoDB Grafana plug-in Now, MongoDB is configured as a data source. To visualize the data through Amazon Managed Grafana, select the Explore tab in the side panel and ensure that MongoDB is selected as the data source. Users can then write the first query in the query editor (see Figure 2). sample_mflix.movies.aggregate([ {"$match": { "year": {"$gt" : 2000} }}, {"$group": { "_id": "$year", "count": { "$sum": 1 }}}, {"$project": { "_id": 0, "count": 1, "time": { "$dateFromParts": {"year": "$_id", "month": 2}}}} ] ).sort({"time": 1}) Figure 2. AMG query editor Grafana will graph the query, illustrating how certain fields change over time. For more granular detail, users can review the data view below the visualization. (see Figure 3). Figure 3. AMG data view Using MongoDB as a data source in Amazon Managed Grafana allows users to easily analyze MongoDB data alongside other data sources, affording a singular point of reference for all of the most important data in an application. There’s no hassle; once connected to MongoDB from Amazon Managed Grafana, it simply works. Try out MongoDB Atlas with Amazon Managed Grafana today.

Moving Across the World and Changing Roles: Meet Jake McInteer

At MongoDB, our employees are empowered to transform their careers and grow in the direction they want to. Jake McInteer is a perfect example of that — after building his career in London at MongoDB on our Solutions Architecture team, he is relocating to Sydney while transitioning to the Enterprise Sales team in the region. Take a look at this interview and learn more about his career path and what he’s most excited for in his new role. Jess Katz: Tell us a bit about how you wound up working at MongoDB Jake McInteer: I’m a Kiwi (New Zealander) who has always had a passion for technology - I think it’s probably in my blood as my parents met at the Government Computing Centre back in the ‘80s and just about everyone on my dad’s side of the family works in technology as well! I tried to be different from my family and study Accounting at university but quickly got bored and switched to an Information Systems degree. After that, I moved into a Consulting role with IBM, but I always felt myself gravitating more toward go-to-market functions. Eventually, I had the opportunity to move to a Presales role in a smaller company specialising in data and analytics and lept at the chance. My time in my first Presales role really confirmed for me how great of a space it is - an intersection between technology and business that gave me an opportunity to work on a wide variety of different things. In 2019, I made the call to move over to London with my partner for some overseas experience and started looking for a new role. MongoDB’s reputation of a high performance culture that was disrupting a market dominated by stodgy legacy vendors really excited me and put them at the top of my list. On landing in London in July 2019, I met with the Solutions Architecture Manager for Northern Europe and together we pushed through a handful of interviews within two weeks. The rest, as they say, is history. JK: What was your onboarding experience like? JM: In one word, incredible. From MongoDB University, through coaching sessions with people across the Solutions Architecture team and trips to HQ in New York City attending Sales Bootcamp and New Hire Technical training - I was left in awe at the resources MongoDB invests to give new hires everything they need to launch their careers at MongoDB. JK: What does a Solutions Architect (SA) at MongoDB actually do? JM: An SA at MongoDB is a technical expert that helps customers understand and evaluate MongoDB. We work closely with the Sales team to help potential customers understand the value of MongoDB as well as when and why to use it. In practice, this means we work closely with our customers’ development teams, with various people spanning software engineers, database administrators, product owners, security specialists, architects and more! We also support our marketing team by running various workshops and webinars. From time to time we also work on our own projects, building out various demos and applications. JK: Tell us a bit about what you’ve been working on as an SA JM: Being an SA at MongoDB has given me the opportunity to work on some of the biggest transformation initiatives of some of the largest companies in the world. I’ve been privileged to work with leading organisations across Financial Services, eCommerce, and even the Air Transport industries while in the role, and on projects that affect millions of customers and billions of passengers - it’s been incredibly rewarding. As we went virtual due to COVID-19, I also ran some of our first virtual-only workshops and webinars, including building out demos and hands-on workshops for developers to complete. JK: So what’s next for you in terms of your career? JM: I’m actually right in the middle of making a big move! My manager and I have always had regular development conversations since I started, and last year I expressed an interest to continue my growth and development into a full-time sales role, as well as my personal desire to move back down under and be a little closer to family in NZ. While I absolutely love the MongoDB team in the UK and have developed friendships here that will last for a lifetime, I am looking forward to further building my career with the team in Sydney. This move is also a career change! With huge amounts of support from my manager and others across the business, I’m making the transition from Solutions Architect to Enterprise Account Executive in Sales. I start my new role at the beginning of September and I’m excited to get started. It’s been awesome being a part of our UK team as it has gone from strength to strength, and I’m excited to get started with our Australian Sales team next. The Australian team is firing on all cylinders and is led by the impressive Jeremy Powers. In my view, it’s a great place, team, and environment for me to make the shift into a full-time Sales role and to continue developing my career all while being closer to family back home. JK: What are you most excited for in your new role? JM: Two things have got me super excited to get started. Firstly, the opportunity to make the transition into an Enterprise Account Executive role and join our formidable sales organisation is an opportunity too good to pass up. Secondly, I’m particularly looking forward to the opportunity to work with businesses in New Zealand and introducing new customers to the incredible technology we offer here at MongoDB. New Zealand has a burgeoning tech sector and some incredibly interesting companies and opportunities - one great example is THL Digital who we’ve done a lot of work with recently. I can’t wait to help them solve some of their biggest challenges and give developers down under a better way to work with data. Interested in pursuing a career at MongoDB? We have several open roles on our teams across the globe , and would love for you to build your career with us!

Intern Series: Making an Impact Across Two Summers - Meet Talía Ayala-Feliciangeli

Talía Ayala-Feliciangeli is a rising senior at Georgia Tech who has spent this summer working remotely as a Product Design Intern. As a returning intern with two summers of remote work on the same team under her belt, Talía is leaving her internship with a unique set of experiences and lessons about #LifeatMongoDB. From the transparency about future visa sponsorship to one-on-one professional development that she’s received, Talía has spent these two summers impressed with the supportiveness of MongoDB’s program and her peers. In this interview, you’ll hear more about what’s made MongoDB a lasting fit. Alex Wilson: Hey Talía! It’s so good to meet you! I want to start this final interview of the Intern Series with one of the questions that I’ve been asking everyone: what brought you to MongoDB? Talía Ayala-Feliciangeli: During my first round of interviews with MongoDB, my recruiter asked me how I would feel about living in New York long term. I remember being super shocked that a recruiter was being so open about what an internship could turn into, especially when she started describing how MongoDB approaches the sponsorship process with employees who are from outside of the U.S. As an international student, it can be challenging to navigate the process of applying to jobs or internships. Unfortunately, not all companies are open to hiring individuals who may require sponsorship at any point in the future. The call with my recruiter was the first time I experienced a company being so open and honest regarding the immigration logistics that international students have to constantly think about, and it made me realize how supportive of a company MongoDB is. Both MongoDB and the specific position I had applied for seemed super interesting, but ultimately what made me decide to intern at MongoDB was the professional support, encouragement, and excitement I felt from the recruiter, the researchers I spoke to, and everyone else I had the chance to meet throughout the interview process! AW: Awesome! It’s so meaningful to see these experiences of openness and encouragement echoed so strongly. What sort of work have you been doing? TA: I work in the UX research team, which is a part of the larger Product Design team at MongoDB. The research team is currently growing, and it's exciting to get to learn different approaches to research through conversations with the new team members! My favorite project so far has been the Atlas Billing Alerts project I'm currently working on. It’s my favorite because due to the nature of the project I’ve gotten the chance to understand how different teams across MongoDB collaborate to build the billing experience, and the participants I’ve spoken to have had very different needs than the user groups I’ve worked with in the past. The stakeholders for the project are closely involved and have provided me with valuable feedback at every step of the project,which has helped me hone my approach to research and have a better understanding of how to translate stakeholder needs into research goals! Plus, I got to meet people throughout different teams at MongoDB which I hadn’t spoken to previously,such as Technical Account Managers and Cloud Support Associates. AW: I think it’s so interesting that besides being a return intern, you’ve also been able to return to the same team. How was your professional experience different the second time around? TA: As a return intern, I had the unique experience of starting the summer already understanding how different teams and processes work at MongoDB. I felt that this knowledge translated into me feeling more confident about my work: onboarding was much quicker, I had context for the projects I was working on, and it was much easier for me to connect with stakeholders for my projects. At times, I felt like a full-time researcher rather than an intern! Plus, having the same mentor both summers meant I got to meet her for coffee and hang out before the internship started this summer,which meant a lot. AW: That’s so great. Having worked remotely both summers, I was wondering if you could speak to the extent that your team supported you virtually? TA: At the start of the summer, my mentor and I had conversations about what I find harder to accomplish when working remotely. After identifying what those things were, we brainstormed ideas of how I could address them and how my mentor could support me with them. For example, I have a harder time staying focused when I’m working remotely from my apartment. My mentor and I decided I would create a detailed timeline breaking down what I needed to do for each of my projects, and we scheduled regular check-ins twice a week so I could share my progress and get her feedback. In general, my team provided a lot of support within this remote work model by creating spaces for me to consistently ask for feedback on my projects or just chat about our approaches to research. In the past I was almost shy about asking for feedback, but my team setting aside time for us to chat about these things despite being remote really helped me grow! AW: That’s definitely an enormous upside of such a collaborative company culture! Have you found that culture to be a positive fit? TA: The culture at MongoDB is incredibly supportive, encouraging, and collaborative. My background is in psychology and research, and I was concerned with how a lack of a technical background could impact my work at MongoDB. Everyone I’ve reached out to has been super friendly and more than happy to share their knowledge (or just have a coffee)! I’ve also really appreciated how encouraging my team members are when it comes to me learning and exploring different interests, be it a side project with another intern, implementing new tools for research, or chatting about the research goals I have. AW: As someone with a political science background, I can definitely understand the fear of coming into the tech industry without a very technical background, so it’s great to hear that you’ve also had such a positive experience tackling that learning curve—thank you for your willingness to share. Finally, I’d love to hear what your favorite thing about MongoDB has been! TA: My favorite part is that I get to have ownership over my work: while my mentor has provided me with constant guidance and support, I’ve always felt that I am given the freedom and trust to decide how to go about my work, from structuring actionable research plans to conducting user studies. While it was intimidating at first, it has been an incredible learning opportunity to understand how to conduct UX research in an industry context! Interested in interning at MongoDB? Our 2021/2022 Software Engineering Summer Internship for the US is now live and accepting applications for students