PHP serverless abstraction framework…

…as serverless architecture picks up steam in the market I predict we will see more and more languages adopting it; is not whole sale from the vendors then from the community itself. As an example here is Bref, a serverless framework for PHP; it can run on it’s own or be used as a bridge for other existing frameworks. Ala Laravel or Slim or CodeIgnitor as AWS Lambda functions. Not a AWS fan? That’s ok, Bref can deploy to any other cloud provider with minimal effort as well. If nothing else, it is worth a read,

https://github.com/mnapoli/bref

AWS Lambda internals

Ran and Nitzan over at epsagon did a two part article on Medium about  AWS Lambda and its internals / runtime environment. It is a pretty interesting read if you are into the serverless architecture specifically or Lambda in general.

NoSQL search results in MICRO-seconds; via AWS’s new DynamoDB Accelerator.

If you have a noSQL data store and need the fast machine possible response time; check this out:

“…Using DAX, you can improve the read performance of your DynamoDB tables by up to 10x—taking the time required for reads from milliseconds to microseconds—even at millions of requests per second….”

I am constantly amazed at the speed some of these services are able to run at, just amazing.

 

The cost of scaling up.

In my time s working in the software realm I have worked on projects of various sizes. Local bands wanting a web presence, user generated content upload sites, college assignments, financial industry video services, national health care web applications, on board ship systems, social media aggregation, US domestic distributor for foreign sourced video content, and currently a software security and end user system monitoring service. Some projects were small, some large, some simple, some complex.

Start ups are well known and sometimes even idolized for their ability to take an idea from concept to production in a very short about of time. In the world of business having a small time to market can mean the difference between success and ruin.

Larger organizations are often scoffed and or even shrugged off due to the exact opposite. However, the larger organizations typically have systems that a dozen startups would get lost inside of. Many times these system have had a dozen or more teams operate and iterate on the system. Knowledge applied, knowledge lost, knowledge incorrectly documented. But at the end of the day bringing the business revenue. Money talks, bulls*** walks.

These two different types of entities have different constraints, different pressures, and different driving factors.  Not every org. can be, nor want to be, Google, or Twitter, or Instagram. Then again, not everyone wants to be the DoD, Wells Fargo, or General Electric.

Deleting an AWS API Gateway resource.

Because it is not well documented in the AWS docs herein is how you delete an AWS API Gateway resource.

  1. Click on the end point in the left hand side.
  2. Click the action button in the top middle, just right of the resource list.
  3. Click the delete option.
  4. Enter the name of the resource and click delete.

Wait 20 – 30 seconds and reload the page. You should no longer see the API resource listed.