Those who followed by Data Governance 101 6-part series, ask me a multitude of scope questions about how to set up their data governance programs.
Several times, I get startling questions, sometimes naive, sometimes overthinking the application of various industry tools and methodologies.
Given the lack of quality practitioners in the industry (Financial Services, or otherwise), it is not surprising to hear those, I figured I will share some of my insights.
I won’t regurgitate the foundations from my past series, but rather I would focus on major program-level mistakes that are tough to “take back” if you happen to…
As large enterprises move to the cloud, a multi-cloud strategy is defined anywhere from, each line of business can choose a cloud provider (e.g., CMO choosing GCP whereas CIO chooses AWS or Azure) to organizations ability for any given application to run in any cloud or on-premise.
Very divergent and orthogonal definitions of what a multi-cloud means to them.
One common issue, how do we make the data and data services available between CSPs (Cloud Service Providers), without building large integration projects whilst giving up availability requirements.
One SaaS platform, I came across, was promising to address these problems with…
From Wall Street to K-Street, everyone is up in arms about Robinhood, as a Financial Services Technologist, I believe we need to find a longer-term solution for this ‘problem’.
I also strongly believe, engineering can solve it for the industry!
I hate to single out, Robinhood, I love Robinhood, but it was just flashier news, so you know, several other brokers put restrictions on these trades as well.
Robinhood, however, should have done better damage control.
As the appetite to build critical operational platforms on the cloud is ever-increasing, CIOs and regulators are increasingly asking for proofs to demonstrate high uptime, resiliency, and minimum or no data loss solutions. Yes, all of it!
I have written about how to measure this uptime formally in the past, here. But, how do you build these applications?
Platform and Cloud Providers (even before there was such a thing as the cloud) have been publishing blueprints for very highly available (Oracle calls it Maximum Availability Architectures) application and data platforms.
API developers wrestle with myriad ways to manage errors and exceptions related to business logic, infrastructure (databases, other APIs), and unhandled concerns in an ad-hoc way, before constructing a response to a REST call.
If you don’t know the answers to these and how to elegantly manage these, please read on:
If you have blinked you might have missed SpringOne 2020 online.
If you are a tenured JEE developer, you might have heard of SpringOne conferences in general and might have watched videos from previous years.
A couple of logistical niceties this year:
How to practically build APIs has been incorporated into a lot of frameworks (such as Tomcat+Spring, express+Inversify).
How to build APIs that are easily consumable, performant, and resilient requires the art of managing scope and budget for sure, and following best practices, along with what worked for others is key.
Famous Richardson Maturity Model for building REST APIs has been around since 2008. It was then promoted by Martin Fowler in his “glory of REST” article in 2010 and put into practice by several engineers, coincidentally, the same year HTTP PATCH specification was introduced.
I am going to focus on…
Since 2018 (reInvent)/19 release of QLDB, there has been quite a bit of discussion on fit for purpose use cases.
I have talked about the myths of what QLDB is not here, for some background.
Specifically, in Financial Services, where our clients are on AWS (or not — if not, ProvenDB) are looking at specific use cases for QLDB as a centralized, immutable, auditable, and verifiable history of changes.
Now, I completely…
A prospective client once said, “We are starting up a new testing team, we need 20 Java engineers with mortgage domain experience”!
He also said they are trying to shift-left, in a big way!
This was 2017 and somewhat understandable, given the testing stack and the fact that test automation was a big theme for a lot of our financial services clients.
Starting in 2018-2019, I have started seeing signs that, developers asked to be experts in AWS infrastructure setup, VPC (Virtual sub-nets), and yeah, we also want them to validate and remediate security and application pen testing issues on…
Welcome back, and glad you are finding this interesting. We have covered some important ground with the Event loop, Rest and Spread operators, Arrow functions, Destructuring in my Part-1 here. Let’s continue.
We will continue from where we left off <link> in terms of improving your foundations towards being a better Front-end engineer.