The newbie cloud architect diary

A star schema is the simplest style of data mart schema and is the approach most widely used to develop data warehouses and dimensional data marts. The weekly mood My role as a cloud architect is slowing transiting from supporter to enabler . As a supporter, you might make some background noise, but you are not really part of the game, worse you are not part of the staff. That's perfect to observe and learn. Now as an enabler, you might indirectly influence or  contribute to  activities. Enablers are for example advisers and trainers. They aren't working on the field or taking decisions on the border, but they are a useful part of the staff, and feel rewarded by its achievements. In a previous post , we introduced the need to infer and flatten the source schema of some  MongoDB  collection, for the purpose of data analytics. In this article, we'll take intermediary tables aka. Staging area for granted. We will focus on defining the target schema , or the "magic&quo

Snowflake is a Cloud Data Warehouse that is comprehensive to use and probably belongs to the most successful cloud platforms over the last few years. The weekly mood This week slightly challenged my sense of responsibility and communication . It started with some (expected) sign of non-satisfaction from my manager, and ended with some (unexpected) sign of Leadership from me. In fact there are enough areas where I usually put enough of pressure on myself, like for example "delivering what I promised". However, I still definitely need a manager to motivate me for other areas like for example "making things happen". As an outcome, I am currently enjoying a much better team work around our Data Lake project and API Gateway evaluation. It's a shame that this would probably not happen without an external trigger, but that's also the essence of Lifelong learning . This experience reflects the common mistake that people make when focusing on results rather than on o

In this 2nd post dedicated to API Architecture re-design, we show how the API Life-cycle and Developer Portal can support your API Management strategy. The weekly mood My first quarter as a full-time Architect ends in 3 weeks. I realize that even if I had defined some goals, path and methodology during my first week, I had built no 30-60-90-day plan to build the ground for a successful job or career. I know about that magic number of 100 days when people start to wonder if their new CEO or VP delivered as promised, and I assume this happens also to employees. But the most important to me was to do the right think rather than to secure quick wins. After ramping-up in the area of DevOps and working a bit on our Data Engineering, I am now committed to our API Architecture re-design. In a previous post , we focused on the following 2 building-blocks: API Development : We emphasized on OpenAPI Specification v3 (OAS3) as a Contract-First development approach, implemented a Microservice using