March 8, 2021 | Updated: December 2, 2021
과거에는 매우 단순했습니다. 그 때는 기업 데이터라는 분야가 현재 규모의 일부에 지나지 않았습니다. 지금과 같은 규모가 된 것은 얼마 되지 않은 일입니다. 우리는 대부분의 데이터를 정해진 작은 열과 행에 집어 넣습니다. 예전에는 몇몇 트랜잭션 처리, 몇 가지 차트와 그래프, 약간의 비즈니스 인텔리전스로도 아무런 문제가 되지 않았습니다.
물론 다소 과장한 감이 없지 않아 있습니다. 데이터 처리의 한계를 뛰어 넘기 시작한 것은 1964년입니다. 그 해에 세계 최초의 항공사 승객 시스템인 SABRE가 2개의 IBM 메인프레임을 토대로 1,500개의 터미널에서 출범하면서 1초당 평균 1건의 트랜잭션을 처리할 수 있게 되었습니다. 그러나 오늘날 데이터는 초창기 데이터와 완전히 달라졌다고 해도 과언이 아닙니다. 첫째, 크기가 59 제타바이트에 달할 정도로 커졌습니다. 둘째, 데이터에 대한 정의가 완전히 바뀌었습니다. 급여 기록 및 주가를 뛰어 넘어 웹 로그, 위험 평점, 맵, 지문 등 다양한 유형의 데이터가 포함되었습니다.
하지만 아마도 가장 큰 변화는 기업에서 데이터가 맡고 있는 역할일 것입니다. 데이터는 항상 비즈니스 전략을 알리는 데 사용되어 왔습니다. 하지만 오늘날에는 데이터가 곧 비즈니스 전략인 경우가 종종 있습니다. 이렇게 생각해보십시오. 20년 전만 해도 CDO(Chief Data Officer)라는 직책 자체가 없었습니다. 오늘날은 어떻습니까? 포춘지 선정 1000대 기업의 2/3 정도가 CDO를 두고 있습니다.
그 이유는 무엇일까요? 그 어느 때보다 데이터에 대해 요구하는 것이 많아졌기 때문입니다. 당연한 얘기입니다. 디지털 경제에서는 모든 기업이 인사이트 기반의 혁신을 토대로 경쟁합니다. 이러한 혁신 덕분에 점차 더 영리해진 알고리즘을 중심으로 소프트웨어가 개발되고 있습니다. 이러한 알고리즘을 개발하고 실행하는 원 재료가 되는 것이 바로 데이터입니다. 데이터를 효율적이고 효과적이며 신속하게 관리할 수 있는 능력이 모든 산업 분야, 모든 기업의 전략 과제가 되었습니다.
지난 20년 동안 데이터의 양과 다양성, 전략적 중요성에 있어 급격한 변화가 있었지만 많은 기업들이 데이터 관리 방법을 바꾸지 않았습니다. 물론, 기존의 관계형 데이터베이스는 유연성이 부족하고 확장이 불편하기 때문에 오늘날 애플리케이션 개발 요구를 처리하기에는 적합하지 않습니다. 그럼에도 불구하고 계속 사용되고 있습니다. 이러한 문제를 해결하려는 노력의 일환으로 2000년대 말 "NoSQL" 운동이 전개되었습니다. 그리고 MongoDB가 최초로 문서 지향 데이터베이스를 발명하게 되었습니다.
그러나 제가 말씀드리고 있는 것은 더 광범위한 것입니다. 즉, 데이터 활용 방법에 대한 새로운 시각을 요구하는 더 장기적인 추세에 관한 것입니다. 다양한 데이터 세트의 기본적인 요구사항이 그냥 변화하는 것이 아니라 수렴되고 있다고 고객들은 말합니다. 이는 놀라운 변화입니다. 지난 50년 동안 줄곧 사일로화되고 전문화된 도구라는 추세가 뒤집히고 있습니다.
한 발 물러서 생각해봅시다. 수십 년 동안 기업들은 레코드 시스템과 인게이지먼트 시스템을 유지해왔습니다. 레코드 시스템은 기본적이고 미션 크리티컬한 진실 공급원으로, 내부 프로그램과 사용자가 주로 액세스합니다. 인게이지먼트 시스템은 고객과 직원이 상호 작용할 때 사용하는 디지털 인터페이스입니다. 최근에는 다양한 소스에서 나온 데이터를 통합하여 전사적 차원에서 의사 결정에 필요한 정보를 제공하는 인사이트 시스템이 추가되었습니다. 오랜 세월 각 시스템은 상주하는 컴퓨터가 서로 달랐고, 데이터 관리 요구사항도 서로 달랐으며, 자금을 대는 부서도 서로 달랐습니다.
하지만 이러한 추세가 변화하고 있습니다. 엄격하게 분리되었던 백 오피스와 프론트 오피스 간의 경계가 허물어지면서 모든 데이터 시스템이 하나가 되어 비즈니스를 수행하는 시대가 되었습니다. 신속하면서도 정확해야 하고, 접근이 쉬우면서도 안전해야 합니다. 또한 트랜잭션과 분석을 모두 처리할 수 있어야 합니다.
특히, 모델 훈련 및 추론이 새롭게 떠오르면서 다양한 유형의 분석이 등장하고 있습니다. 사람이 질문을 하고 모델을 구현할 프로그램을 작성하는 것이 아니라, 프로그램이 시스템에 인사이트 관련 질문을 하고 실시간으로 이에 대응하는 방식으로 바뀌고 있습니다. 이는 그야말로 근본적인 변화입니다. 마치 SABRE의 기반이 IBM 7090에서 SKYNET으로 바뀌는 것과 같습니다.
이러한 데이터 요구사항의 “수렴"은 도전 과제이자 기회입니다. 문서 데이터베이스 덕분에 데이터의 액세스 및 저장 방법을 재고할 수 있었던 것처럼, 이러한 수렴 현상 덕분에 데이터를 전사적으로 관리하는 데 사용하는 시스템을 다시 한 번 재고해야 하는 상황이 되었습니다. Snowflake부터 Databricks, MongoDB에 이르는 업계의 모든 기업들과 모든 클라우드 제공업체들은 정보에 입각한 실시간 의사 결정을 뒷받침하는 마이크로서비스 기반의 네트워크 또는 프로그램을 사용해 데이터로부터 더 많은 가치를 창출할 수 있는 시스템을 제공하기 위해 노력하고 있습니다.
재미있는 것은 혁신을 추구하는 소프트웨어 중심의 클라우드 기반 기업이 되기 위해 대부분 기업들이 획기적인 디지털 전환 프로젝트를 진행하고 있는 시점에 이러한 추세가 등장했다는 사실입니다. 다시 말해 모두가 이미 발 빠르게 움직이고 있습니다만, 지금이야말로 데이터베이스를 재고해 보기에 가장 적합한 때입니다. 데이터를 복사하거나 이러한 복사 작업을 눈에 보이지 않게 수행하지 않고 모든 관련 데이터 세트를 토대로 데이터를 실시간으로 처리, 저장, 보호 및 분석할 수 있는 실질적인 "데이터 플랫폼"을 설계할 수 있는 절호의 기회입니다.
저는 앞으로 몇 달에 걸쳐 이러한 데이터 플랫폼이 어떻게 설계되어 있고, 어떻게 최신 애플리케이션 개발을 지원하는지에 대해 자세히 알려드릴 계획입니다. 또한 오늘날 기업들이 할 수 있는 것과 할 수 없는 것을 살펴보고 현실의 문제를 해결하기 위해 어떤 제품들이 개발될 것인지 예측해 보면서 안개가 낀 듯 막연하기만 한 미래를 여러분과 함께 더듬어 가볼 생각입니다.
하지만 지금은 데이터베이스라는 기업 자산에서 어떤 일이 벌어지고 있는지 들어보고 싶습니다. 여러분도 이와 비슷한 데이터 요구사항의 수렴을 경험하고 계십니까? 그렇다면 디지털 전환 전략에 이러한 트렌드를 반영하고 계십니까? 아니라면 전사적 차원에서 데이터를 사용하는 방법에 있어 어떤 변화가 나타나고 있습니까? 제게 연락하고 싶으신 분들은 이 블로그나 Twitter(@MarkLovesTech)를 이용해 주시기 바랍니다.
읽어주셔서 감사합니다. 다시 만날 때까지 데이터가 여러분의 편이 되어주기를 바랍니다. Mark
Transitioning from Teacher to MongoDB’s New Enterprise Modernization Team: Meet Gabriela Preiss
As a global company, MongoDB has amazing employees with interesting backgrounds and stories. I recently sat down with Gabriela Preiss, an Enterprise Modernization Consultant, to learn more about her journey across the globe from the U.S. to Barcelona, Spain, and her experience transitioning from teaching to becoming the first hire for MongoDB’s brand-new Enterprise Modernization Team, shifting enterprises toward innovation and generating a ton of compelling content along the way. Andrew Bell: Thank you for sharing your story, Gabriela. I’d love to know how you got to where you are today in your role. What skills are important for someone on your team to be successful? Gabriela Priess: My career journey has been from one end of the spectrum to the other. Originally, I studied English and education, and I was a high school teacher for four years. I loved teaching, and I encourage anyone who wants to pursue it to do just that, but eventually, I hit a block and craved more mobility. So I moved from the U.S. to Portugal and studied web and mobile development. Finding myself back as a junior in a new industry, I worked my way up by freelancing as a web developer, building a curriculum for a coding school, and then quickly finding my way into a lead tech support role with a popular web application organization, where I also led the QA process. So, how does all of this add up to working in and with data? I truly believe every professional experience is the chance to extract something positive — a learning takeaway. This diverse background has challenged me and shaped me, as well as helped me to be confident in my choices, to trust I’m taking steps in the right direction, because ultimately each career move has been better than the last and has led me to where I am now, with MongoDB, as an Enterprise Modernization Consultant. Ultimately a career risk led me to a job that didn’t even exist a year ago on a new team. So, we can never truly say what the future holds for us; we may be headed toward a killer career that hasn’t even been invented yet. When it comes to being successful on my team, I think this role is open to so much diversity. I’m trying to narrow down any specific skills, but I think anyone who is ambitious, independent, takes ownership with what they produce, and is curious will succeed here. Curiosity is a huge asset — someone who is open to learning and diving deep into what they don’t yet understand, eager to keep growing, and tech-curious. A big part of what we do involves us keeping our finger on the pulse of tech and data innovation, so we can confidently discuss, debate, or write about it. This means feeding ourselves with the right tech news content. AB: I’d love to know more about the modernization team. What’s your role and your day-to-day like? GP: Our reach is quite broad, but if I had to define it, I’d say the Enterprise Modernization Team (EMT) assists, educates, and helps inspire large enterprises to move toward modernization and innovation. Often, large enterprises have the most complex, costly legacies in their systems and need macro and micro aid and insights to not only modernize but also to visualize and tally the endpoint. EMT Principles and Consultants have the industry expertise and capability to translate our value proposition to senior executives and engineering management. This includes generating training content for internal teams; meeting with other teams for potential and ongoing accounts; delivering webinars, published content, and interactive exposition presentations; and meeting with clients so they have a stronger understanding of how MongoDB helps them to modernize from the most basic format, such as adopting the document model, to truly leading in innovation, such as data science, machine learning, and real-time analytics. So, EMT is a bridge between sales, technical sales, and marketing for complex industry use cases and solutions. These are the teams we collaborate most often with, working closely with sales reps and solutions architects, collaborating with solution providers, and closely aligning with the marketing team producing diverse content and product alignments. So, if you ask me what exactly is my role, I’d say it’s all of the above. Our team is small, although it’s growing quickly, and we have big plans to expand exponentially in the near future. That said, we have a democratic way of dividing the work. We’re made up of our Global Head, Boris Bialek, our Principal, Steve Dalby, and the two Consultants, including myself and Vanda Friedrichs. And we’re all expected to bring equally to the table, despite who has more seniority. This lets us all have an idea of what everyone is working on, and we frequently dip into each other’s projects either to help out or request aid. Each project is free roaming for all: as long as we’re aware of the objective and deadline, we can get creative with how we reach the endpoint. My projects are constantly evolving and regenerating, and I could joke that the only thing they have in common with each other is they all have to do with MongoDB. However, when I was hired, Boris was very clear and direct that each day would be different, and his promise has held true. I don’t have a day-to-day like most others might in regard to consistent projects, but the objective is always the same for each: how can we showcase MongoDB’s value in modernization and innovation in regards to data and tech? Because my projects are so diverse, and often more creative-oriented than anything else, I make up for what some may call a “lack of structure” by being very structured in how I plan my day. Before each day, I predetermine how my next day is going to be divided hourly by projects, tasks, and follow-ups, and I reserve some time for “self-learning,” where I take time to continue my training curriculum, since that’s an ongoing track. AB: Since this is a new role, what tools and resources (e.g., Sales Bootcamp) were you given to help you ramp up? GP: True, this was a new role when I first stepped in, so I didn’t totally know what to expect. There was a running joke I was learning by a fire hose, just having everything blasted at me, and something was bound to stick. MongoDB sets all employees up with boundless learning resources, so I created a curriculum for myself. I prioritized from the top down, based on what I needed to understand ASAP, such as MongoDB’s services and functions, and from there I had freedom to roam based on what interested me the most and what my weak spots were, and was given time to dive in deep technically. For example, I ran POVs to see the data in action from a locally set up database. I know other teams within the company have established curriculums for onboarding, but because this was a new role, I used the resources available and that worked for me. I was given a lot of liberty with my learning because it was mostly autonomous and self-driven, but that’s not to say my learning is over. The company really promotes a learning culture, and every week there are new resources with webinars, learning materials, training materials, and so on. Early into my onboarding, I participated in what’s called our Sales Bootcamp. It’s a two-week intensive training that dives deep into MongoDB’s services as a whole and lays a strong foundation to build on. It’s usually something that’s done in person at MongoDB’s headquarters in New York City, but since this is the COVID-19 era, it was done virtually, with a big cohort of new hires included from Europe and the Americas. This was a cool experience, because I got to meet a lot of new faces. Professionally, my background is originally in education, so I used to write my own curricula for my students, and I’ve been impressed with what I find the MongoDB enablement and Learning & Development teams generating. AB: What content have you and will you create? What is the purpose of this content? How is it leveraged? GP: Among many other roles, the EMT is a content-generating team, so we’re constantly working on creating something new, or collaborating with other teams to create new content. As of today, I’ve been with MongoDB for four months, and in that short time, I’ve been able to generate a lot of interesting, challenging pieces. Each project I’m given is a chance to dive deeper into that subject and expand my understanding of it — like data science or fintech, for example. One of the first projects I had was the chance to write a blog about MongoDB’s partnership with Iguazio , and how our data platform is the ideal persistence layer for Iguazio’s data science and MLOps platform, which is used to develop, deploy, and manage AI applications. Clearly, each project is a team effort, but this gave me the opportunity to dive into a topic I find personally interesting, while building connections with some of our most innovative partners. My first or second week I was introduced to an internal deck created by one of our Solutions Architects, Pascal Jensen. It was a sort of think piece on how data is being driven by the growing uncertainties of the world, in a political, social, and economic sense, and how the most innovative leading companies are responding. We decided to turn this into a more holistic, complete white paper to reach a wider audience. With that, after really digesting the deck that was available and multiple interviews with the Solutions Architects that contributed to it, I built an extensive paper around it, giving breath to the expression “digital by default.” This was something I was quite proud of, because it was so early on in my time with MongoDB, and it let me dive into truly interesting topics. I was able to build on the holistic elements of data and how it’s reshaping even the most mundane elements of the world, propelling us into the future with innovative technologies and solutions for some of the most crucial global concerns, such as hunger or healthcare. Last month, I presented my first corporate webinar with MongoDB, discussing transitioning from a relational database to MongoDB’s document model. It was a huge opportunity, because we were focusing on Spanish-speaking countries in Latin America. For me, this was almost a beta project, because I didn’t know what to expect in regard to reception. In the end, it was a massive success: overall, we had more than 6,500 registrants. That was a really exciting experience, because I knew as a team and a company we were clearly doing something right, engaging with the right audience, and connecting with the right people. There is a really positive response still outpouring from that webinar, and I was happy to be a part of it, especially as a rookie. Again, it just speaks to how much autonomy and freedom to create I’ve been given. My manager never holds me back from any opportunity and really encourages our success. In the spring, we’ll repeat the same endeavor with another webinar, covering a different topic I’m currently preparing in Spanish. AB: What was it like starting in a new role on a new team, especially during the pandemic? How do you stay connected to the team despite living in different countries? GP: Despite the pandemic, there was a lot to dive into because the company was running full speed ahead. It can be slightly intimidating being the new person on a fast-paced team, but I felt very included and seen from day one, and there was more than enough work and training to keep me busy. I haven’t really considered what it would’ve been like to work with MongoDB prepandemic, because at this point, this is all I’ve known. Staying connected with my direct team, though, has been the easiest part for me. I’ve never once felt disconnected despite never having met them in person. As of now, we’re dispersed across Dublin, London, Zurich, and Barcelona, and we’re growing. Plus, our backgrounds are even more diverse considering where we’ve lived, where we’re from, and the languages we speak. It’s refreshing to be part of a team that doesn’t feel limited to one geographic region, because it opens our minds and team discussions to diverse views and ideas. AB: How would you describe the team’s culture? And how do you maintain this culture during COVID-19? GP: The team culture is really positive, inclusive, and ambitious. Every team meeting feels like a brainstorming session, because part of our job is innovation. We’re all given a voice and are expected to use it as we shuffle through ideas and ongoing projects. But overall, our team culture is casual, in the sense that we engage with each other informally, but we all recognize what we need to be working on and by when. We’re each expected to take ownership of our work, and we’re given a lot of creative and structured autonomy. This means independently owning whatever it is we’re working on, and this goes for professional learning too. MongoDB creates a lot of resources internally that I take advantage of, from guided training and courses to reading material, interactive training, webinars, and so forth. I was paired up with one of our Solutions Architects, Benjamin Schubert, and he patiently made himself available to help guide me through some of the more technical aspects of our databases as I was learning how to maneuver through it myself, and I am eternally grateful. Of course, we have support any time we need it, and I can easily seek out resources or set up a Zoom call with an internal expert if I have any questions, but at the end of the day, the ticker moves forward only if everyone is doing their part, so each of us takes our part seriously. Interested in pursuing a career at MongoDB? We have several open roles on our teams across the globe , and would love you to build your career with us!
Manufacturing at Scale: MongoDB & IIoT