At the end of the day, it is still Parquet at the bottom. So, it has a big player data vendor reading in and out of it. The decisions I'm looking at is that there's two standards based ways to store big data Apache Iceberg and Delta Lake, and both are open source.Īpache Iceberg probably has more contributors because it's used by Snowflake. And Ed will tell me because he is used it more than I have. Where is the lock in with Fabric? I do not think there is one. You have a migration path in, you have a migration path out. So, the tech works, its proven other vendors are using it. Delta Parquet is an industry standard, there was a great article about Apple using petabytes worth of data on Databricks in Delta Lake. So you've got a migration path in and a migration path out. The APIs you used to get at it have been around for years, so other tools integrate with them. If OneLake were to vanish, your data would still be in Data Lake Gen 2. And if you think about where all the data in Azure is stored, OneLake's built on top of it. It is in every enterprise business in the world. Power BI as a platform is very well adopted. But what you could do is look at the decisions they made to move forward. Because they made mistakes, and people have been burnt by those mistakes. If you look at Microsoft's past performance, you may decide that you do not want to bet. You have got to be careful and understand that past performance is not a predictor of future success. Just because I work in insurance does not mean I understand the future!īut you must think about it. What is the market going to think of it? It is tough to look into the future and predict whether it is going to fail. That is one of the hesitations with moving quickly with Microsoft Fabric. We try our best to make bets where we are not getting blown out of the water. The ability to distribute our calculations at global scale is a hard problem to solve, but it means that we can go to our customers as a very robust solution. Our Compute Platform is something that we have invested heavily in ourselves. And let us bet on things that have high levels of adoption and are core to the platform. The underlying decision process for us has been "let's bet on open source" because we are not just relying on one vendor to support it. We did manage to sidestep the early data products that did not make it. Tom Peplow: This is going to sound self serving, but we've made some pretty good bets. Technologies in the cloud seem to have a short shelf life. We have already had two versions of Data Lake and Microsoft Azure and now we have got OneLake. But the dark side of this is that things often go away quite quickly as well. Milliman works in the insurance industry, which tends to have quite a long timeframe perspectives a lot of the products have a very long life cycle, it's a heavily regulated industry, so things often tend to move quite slowly, whereas the nature of cloud platforms tends to be very fast iteration and everyone's driving to innovate and get the next thing out there. In this final part, Tom talks about how Milliman resolves the long-term outlook required in the insurance industry with the very fast pace of change that occurs in cloud platforms. You can find a link to the first two parts in the description. Ian Griffiths: This is the third and final part of a discussion of what Microsoft Fabric means for your existing skills and investments in Microsoft Azure's data and analytics services. 05:06 Shielding users from technology changes.02:07 What will the market make of Fabric?. The talk contains the following chapters: How do you deal with these two opposing forces? Can you make good bets by betting on open source and open standards? Can you avoid vendor lock in, without the multi-cloud pitfall of building against the lowest common denominator? Or should you go all-in and bet on a single vendor and take advantage of their innovation investments? Cloud platforms, on the other hand, are fast-paced and evolve quickly. The insurance industry is slow moving, heavily regulated, and products have a long lifespan. Tom Peplow, Principal & Senior Director Product Strategy at Milliman, chats with Ian Griffiths & Ed Freeman from endjin about how Microsoft Fabric is a disruptive technology. In a 3-part interview we talk to Tom Peplow about his assessment of Microsoft Fabric. Welcome to the final part in a new series of interviews with real-world Decision Makers (CTOs, CIOs, Heads of / Directors of Software Engineering, Data & Analytics) about how they manage their strategic roadmap and evaluate new technologies to simplify their portfolio, deliver better outcomes for stakeholders, or give them a competitive advantage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |