The Coupling Point: How I saved $2K/m by Progressively Decoupling Drupal!

Today is an exciting day for me....after years of hard work, i have reached a milestone...

...i have finally reached "The Coupling Point" ™

The Coupling Point, is the point in your application integration, where you can merge 2 different technologies together, for the purpose of creating a better experience for your application users, and for me, most importantly, how to make your application more efficient for the purpose of cost savings on your application architecture to reduce cloud infrastructure costs dramatically!

...breaking a critical scaling barrier.

I just threw away 160 servers and could not be happier!!!...yup, you heard that right... my Patent Pending Ai NLP News Analysis Engine that powers website and Buzzwords Alexa Skill, previously required 80 servers per calculation to complete within 1.5 hours, twice a day autoscaled, about $3K total per month!!!

Today, after Progressively Decoupling Drupal, i can run my calculation 5 times a day, with just 4 server, reducing my EC2 cost by 90% = ~$1,800 per month!

That is the true power of the cloud, to be able to spin down waste on demand...

...and i am going to tell you all about how i did what i did...

live, learn & teach.

No magic, this is the cause & effect of R&, optimizing, reengineering, rearchitecting, testing, scaling, perseverance and breaking barriers!

In my case, Decoupling my Drupal 8 application , will reduce my total costs by an estimated 50%!

Let's take a look at some "before & after" graphs, shall we...

COSTS BEFORE / AFTER Progressively Decoupling Drupal: v1 vs v2

In the bar chart below, you can see, on the day of the cutover, costs cut by 50%!

...there are 2 types of satisfactions in business...making money, and saving money...and the latter is almost as good as the former...

there is a cost to every scaling point.

$3K, ouch!!!!

EC2 details:

RDS DB details: