It is a visitor put up co-authored by Michael Davies from Open Universities Australia.
At Open Universities Australia (OUA), we empower college students to discover an enormous array of levels from famend Australian universities, all delivered by on-line studying. We provide college students various pathways to realize their academic aspirations, offering them with the pliability and accessibility to achieve their tutorial targets. Since our founding in 1993, now we have supported over 500,000 college students to realize their targets by offering pathways to over 2,600 topics at 25 universities throughout Australia.
As a not-for-profit group, value is a vital consideration for OUA. Whereas reviewing our contract for the third-party device we had been utilizing for our extract, remodel, and cargo (ETL) pipelines, we realized that we may replicate a lot of the identical performance utilizing Amazon Net Providers (AWS) providers corresponding to AWS Glue, Amazon AppFlow, and AWS Step Capabilities. We additionally acknowledged that we may consolidate our supply code (a lot of which was saved within the ETL device itself) right into a code repository that may very well be deployed utilizing the AWS Cloud Growth Equipment (AWS CDK). By doing so, we had a chance to not solely cut back prices but additionally to boost the visibility and maintainability of our information pipelines.
On this put up, we present you the way we used AWS providers to exchange our current third-party ETL device, bettering the staff’s productiveness and producing a major discount in our ETL operational prices.
Our method
The migration initiative consisted of two principal components: constructing the brand new structure and migrating information pipelines from the present device to the brand new structure. Usually, we might work on each in parallel, testing one element of the structure whereas growing one other on the similar time.
From early in our migration journey, we started to outline just a few guiding rules that we might apply all through the event course of. These have been:
- Easy and modular – Use easy, reusable design patterns with as few shifting components as doable. Construction the code base to prioritize ease of use for builders.
- Price-effective – Use assets in an environment friendly, cost-effective manner. Goal to attenuate conditions the place assets are working idly whereas ready for different processes to be accomplished.
- Enterprise continuity – As a lot as doable, make use of current code slightly than reinventing the wheel. Roll out updates in phases to attenuate potential disruption to current enterprise processes.
Structure overview
The next Diagram 1 is the high-level structure for the answer.
Diagram 1: General structure of the answer, utilizing AWS Step Capabilities, Amazon Redshift and Amazon S3
The next AWS providers have been used to form our new ETL structure:
- Amazon Redshift – A totally managed, petabyte-scale information warehouse service within the cloud. Amazon Redshift served as our central information repository, the place we might retailer information, apply transformations, and make information obtainable to be used in analytics and enterprise intelligence (BI). Notice: The provisioned cluster itself was deployed individually from the ETL structure and remained unchanged all through the migration course of.
- AWS Cloud Growth Equipment (AWS CDK) – The AWS Cloud Growth Equipment (AWS CDK) is an open-source software program improvement framework for outlining cloud infrastructure in code and provisioning it by AWS CloudFormation. Our infrastructure was outlined as code utilizing the AWS CDK. Consequently, we simplified the way in which we outlined the assets we needed to deploy whereas utilizing our most well-liked coding language for improvement.
- AWS Step Capabilities – With AWS Step Capabilities, you possibly can create workflows, additionally referred to as State machines, to construct distributed purposes, automate processes, orchestrate microservices, and create information and machine studying pipelines. AWS Step Capabilities can name over 200 AWS providers together with AWS Glue, AWS Lambda, and Amazon Redshift. We used the AWS Step Perform state machines to outline, orchestrate, and execute our information pipelines.
- Amazon EventBridge – We used Amazon EventBridge, the serverless occasion bus service, to outline the event-based guidelines and schedules that will set off our AWS Step Capabilities state machines.
- AWS Glue – An information integration service, AWS Glue consolidates main information integration capabilities right into a single service. These embody information discovery, trendy ETL, cleaning, reworking, and centralized cataloging. It’s additionally serverless, which implies there’s no infrastructure to handle. contains the flexibility to run Python scripts. We used it for executing long-running scripts, corresponding to for ingesting information from an exterior API.
- AWS Lambda – AWS Lambda is a extremely scalable, serverless compute service. We used it for executing easy scripts, corresponding to for parsing a single textual content file.
- Amazon AppFlow – Amazon AppFlow permits easy integration with software program as a service (SaaS) purposes. We used it to outline flows that will periodically load information from chosen operational programs into our information warehouse.
- Amazon Easy Storage Service (Amazon S3) – An object storage service providing industry-leading scalability, information availability, safety, and efficiency. Amazon S3 served as our staging space, the place we might retailer uncooked information previous to loading it into different providers corresponding to Amazon Redshift. We additionally used it as a repository for storing code that may very well be retrieved and utilized by different providers.
The place sensible, we made use of the file construction of our code base for outlining assets. We arrange our AWS CDK to confer with the contents of a particular listing and outline a useful resource (for instance, an AWS Step Capabilities state machine or an AWS Glue job) for every file it present in that listing. We additionally made use of configuration recordsdata so we may customise the attributes of particular assets as required.
Particulars on particular patterns
Within the above structure Diagram 1, we confirmed a number of flows by which information may very well be ingested or unloaded from our Amazon Redshift information warehouse. On this part, we spotlight 4 particular patterns in additional element which have been utilized within the last resolution.
Sample 1: Knowledge transformation, load, and unload
A number of of our information pipelines included important information transformation steps, which have been primarily carried out by SQL statements executed by Amazon Redshift. Others required ingestion or unloading of information from the information warehouse, which may very well be carried out effectively utilizing COPY or UNLOAD statements executed by Amazon Redshift.
Consistent with our intention of utilizing assets effectively, we sought to keep away from working these statements from throughout the context of an AWS Glue job or AWS Lambda perform as a result of these processes would stay idle whereas ready for the SQL assertion to be accomplished. As a substitute, we opted for an method the place SQL execution duties can be orchestrated by an AWS Step Capabilities state machine, which might ship the statements to Amazon Redshift and periodically test their progress earlier than marking them as both profitable or failed. The next Diagram 2 reveals this workflow.
Diagram 2: Knowledge transformation, load, and unload sample utilizing Amazon Lambda and Amazon Redshift inside an AWS Step Perform
Sample 2: Knowledge replication utilizing AWS Glue
In instances the place we wanted to copy information from a third-party supply, we used AWS Glue to run a script that will question the related API, parse the response, and retailer the related information in Amazon S3. From right here, we used Amazon Redshift to ingest the information utilizing a COPY assertion. The next Diagram 3 reveals this workflow.
Diagram 3: Copying from exterior API to Redshift with AWS Glue
Notice: An alternative choice for this step can be to make use of Amazon Redshift auto-copy, however this wasn’t obtainable at time of improvement.
Sample 3: Knowledge replication utilizing Amazon AppFlow
For sure purposes, we have been in a position to make use of Amazon AppFlow flows rather than AWS Glue jobs. Consequently, we may summary among the complexity of querying exterior APIs instantly. We configured our Amazon AppFlow flows to retailer the output information in Amazon S3, then used an EventBridge rule based mostly on an Finish Circulate Run Report occasion (which is an occasion which is printed when a circulate run is full) to set off a load into Amazon Redshift utilizing a COPY assertion. The next Diagram 4 reveals this workflow.
Through the use of Amazon S3 as an intermediate information retailer, we gave ourselves larger management over how the information was processed when it was loaded into Amazon Redshift, compared with loading the information on to the information warehouse utilizing Amazon AppFlow.
Diagram 4: Utilizing Amazon AppFlow to combine exterior information to Amazon S3 and replica to Amazon Redshift
Sample 4: Reverse ETL
Though most of our workflows contain information being introduced into the information warehouse from exterior sources, in some instances we wanted the information to be exported to exterior programs as an alternative. This fashion, we may run SQL queries with advanced logic drawing on a number of information sources and use this logic to help operational necessities, corresponding to figuring out which teams of scholars ought to obtain particular communications.
On this circulate, proven within the following Diagram 5, we begin by working an UNLOAD assertion in Amazon Redshift to unload the related information to recordsdata in Amazon S3. From right here, every file is processed by an AWS Lambda perform, which performs any needed transformations and sends the information to the exterior utility by a number of API calls.
Diagram 5: Reverse ETL workflow, sending information again out to exterior information sources
Outcomes
The re-architecture and migration course of took 5 months to finish, from the preliminary idea to the profitable decommissioning of the earlier third-party device. Many of the architectural effort was accomplished by a single full-time worker, with others on the staff primarily helping with the migration of pipelines to the brand new structure.
We achieved important value reductions, with last bills on AWS native providers representing solely a small share of projected prices in comparison with persevering with with the third-party ETL device. Shifting to a code-based method additionally gave us larger visibility of our pipelines and made the method of sustaining them faster and simpler. General, the transition was seamless for our finish customers, who have been in a position to view the identical information and dashboards each throughout and after the migration, with minimal disruption alongside the way in which.
Conclusion
Through the use of the scalability and cost-effectiveness of AWS providers, we have been in a position to optimize our information pipelines, cut back our operational prices, and enhance our agility.
Pete Allen, an analytics engineer from Open Universities Australia, says, “Modernizing our information structure with AWS has been transformative. Transitioning from an exterior platform to an in-house, code-based analytics stack has vastly improved our scalability, flexibility, and efficiency. With AWS, we will now course of and analyze information with a lot sooner turnaround, decrease prices, and better availability, enabling fast improvement and deployment of information options, resulting in deeper insights and higher enterprise selections.”
Further assets
Concerning the Authors
Michael Davies is a Knowledge Engineer at OUA. He has intensive expertise throughout the training {industry}, with a specific deal with constructing sturdy and environment friendly information structure and pipelines.
Emma Arrigo is a Options Architect at AWS, specializing in training prospects throughout Australia. She focuses on leveraging cloud expertise and machine studying to handle advanced enterprise challenges within the training sector. Emma’s ardour for information extends past her skilled life, as evidenced by her canine named Knowledge.