We've made it to the final day, the 12th day of AWS!
Talking of RDBMSs, with all of the Data Lakes, Data Warehousing, NoSQL solutions available on AWS, it is nice to still have access to a good old RDBM, which Aurora provides, with both MySQL and PostgreSQL flavors.
To talk about Redshift we probably need to talk about Data Warehousing, as Redshift is a fully managed Data Warehouse package. This is not putting your data in a ‘digital warehouse’ to go and gather virtual dust on the back of a virtual shelf somewhere and is more akin to a single source of truth for the state of a business and its information. Whilst Redshift is based on PostgreSQL and can be queried with normal SQL, it is not meant to be a DataBase per se.
Extract, Transform & Load (ETL) is the name of the game when it comes to Data Pipelines.
The Extract portion will acquire data from some source(s), which will then pass through Transform where some alteration may be needed to that data, to then end up Loaded into another storage format, such as Redshift, S3, to name a couple.
Despite being what most people think about when mentioning AWS, I left their Elastic Compute Cloud (EC2) until now, mostly because personally I don’t use it all that much.
With the advent of Lambda, EC2 can feel a bit more laborious as there is a lot more set up involved than with serverless solutions.
It’s that time again, another DrupalCon is fast approaching and our team couldn’t be more excited for this year’s Seattle event. We’ve got a lot in store for you this year, from presentations, BOFs, sponsorships, partnership collaborations, and using our listening ears. You’ll find our team distributed all about.
We’re bringing a stacked line-up of knowledge and experiences to drop on 'ya this year. Not only that, we’re looking forward to hearing all the ups and downs you’ve had this past year, and how we’re all growing together within the Drupal community.
Let’s get to sharing!
Nowadays everyone has an API and it's fairly common to want a website you're working on to fetch data from a 3rd party API. That's because pulling 3rd party data into your website can not only enriches your website's content, but doing so can prevent the need to duplicate commonly needed data.
API provided data could include displaying weather information, going through drupal.org projects, looking through census results, or even displaying Magic the Gathering card data. In fact, every WordPress site comes with an active JSON API out of the box.
There really is an API for almost anything. It's no surprise that you'll eventually want to consume some random API while developing a Drupal website. But enough of the sales pitch, let's get started consuming JSON APIs.
Jill Cohen is a Senior Software Application Engineer at Autodesk Inc. Autodesk is a global company that empowers users to design and create just about everything on this planet - and in virtual worlds. She works with the Digital Platform and Experience Organization on the Digital Help team, which manages the Autodesk Knowledge Network and Services Marketplace. She is also on the board for Autodesk Women in Leadership.
One of the major objectives of Drupal 8 is the desire to “get off the island.” Drupal opened its doors to using and contributing to a broader ecosystem of projects instead of replicating functionality in Drupal. We now see tools like Twig and various Symfony components in Core. Contributed modules are also able to integrate projects and Software Development Kits (SDKs). For example, Password Strength, Digital Ocean, and Hubspot API integrate through Drupal’s native use of Composer. This philosophy helps those of us that more closely identify as “Drupal Adjacent.”
Recently I spent three days at O’Reilly’s Strata Data Conference learning just how broad and deep the Big Data space has become. The sessions were interesting, the tutorials informative, and the keynotes were inspiring. The keynotes are available online.
