Last weekend (from Friday 29th Oct to Tuesday 2nd Nov), was the #BuildWithAI Hackathon 2021 where participants, mentors, sponsors and organisers gathered together to solve real world challenges with AI. This event does not standalone. In a world full of change, this (from my perspective) started last year in the #BuildWithAI Hackathon 2020 and continued to build.
This article is about the event but the event itself is just “Another Step”.
I’m taking a small break in transmission to talk about something else. I’m referring to the #DaysOfArm articles that I’ve been writing about (here). Yesterday and for the past few weeks, we’ve been running a pilot of a 4-part webinar series which we’ve called Oracle Tech Talks. Let me explain.
At the #WorldInnovationDay Hackathon, Apr 16-19 saw many participants and teams come together to progress the agenda around the United Nations #SustainableDevelopmentGoals. I’ve previously wrote about this hackathon – you can check these articles about the technology (here) and about the event (here).
April 16-19 saw people from across the world come together to focus on three Sustainable Development Goals (SDGs) at the #WorldInnovationDay Hackathon. This blog highlights the technologies used to help accelerate the team’s execution. If you want to read more about the event itself – check out this previous blog (here).
Over the course of the weekend, Oracle Cloud tenancies with $500 USD credits were provided to each participant to use. It was not mandated that they use Oracle Cloud nor was it given to participants automatically. It was encouraging to see people open to explore and learn with Oracle Cloud. I want to thank the Oracle mentors supported the participants ensuring that whilst the teams explored, they could confidently execute and deliver. Here are the common requests from teams and the cloud services that they used over the weekend.
If you had come here because of the link in the information pack, great. If you have come here because you found this page through other means – read on and if you are inspired to contribute (on April 16-19) – head to the Hackmakers site (here) to register for this event.
In closing out 2020 and before going on leave, I was given an opportunity (never a challenge). And it came in the form of these Oracle Code Cards. For those that haven’t seen them, this is what they look like and here is a git repository of some code explaining more about the cards themselves that I’m revamping – https://github.com/jlowe000/codecard.
The outcome required was as open as I could get.
There were no boundaries and there were no specific rules.
Last weekend saw over 2,000 people participate in the #DigitalDefence Hackathon hosted by Hackmakers, Oracle as the lead sponsor plus a vast range of other sponsors – ITIC, AustCyber, NASSCOM CoE, Cyber Security Centre of Excellence, IBM and community partners – Public Sector Network, Slack, Black Nova Group, Yirigaa, UNSW DataSoc, SLASSCOM, DataCated Academy and DataEthics4all.
This event was off the back on #BuildWithAI Hackathon hosted by Hackmakers. Being a contributor to that event as a Lead Mentor, Sponsor and a Challenge Organiser, there was something there that resulted from what we were able to deliver – another step in the infinite game. (Note – I haven’t read the book, I don’t follow Simon Sinek however from different communities and framework where we focus on growth mindsets, long tail and talking about your why – this is another example of that same conversation).
Testing BookInfo app with Circuit Breaker based policy
The third and last test in the Service Mesh, is using a Circuit Breaker based pattern. It further protects our microservices in case of certain conditions occur, such as preventing that an unexpected number of requests overflow and affect the microservices in the service mesh.
We might decide to throttle or simply reject new incoming requests when a number of current incoming http requests reaches certain threshold.
For demonstration purposes, we are going to set rules to allow a maximum of 1 request at a time. If more than 1 request comes in, we will prevent it from entering the mesh.