mdx-bundler VS aws-lambda-java-libs

Personally using https://github.com/kentcdodds/mdx-bundler

Exact code could be different if you're using mdx-bundler, Contentlayer, or anything else. But there should be a similar API for adding components.

mdx-bundler

Do note that Code Hike also works with Next MDX Remote and MDX Bundler however, we are going to look at a simple example with the official MDX plugin for Next.js.

i'm having a hard time finding a solution, just like others → https://github.com/kentcdodds/mdx-bundler/issues/70

Depends on what functionality you'd like to add as you go. I recently built my site from scratch (with no prior experience) using NextJS, MDX and mdx-bundler [1]. Having the ability to add custom components, or statically generate a related posts matrix are all super useful.

1: https://github.com/kentcdodds/mdx-bundler

https://olickel.com

MDX Bundler differs from all of the other packages listed above in that it is Framework agnostic, meaning you can use it outside of Next.js. Like next-mdx-remote, no changes to the next.config.js file are necessary.

To make Next.js works with MDX, we need to compile and bundle the markdown files. For this task, I decided to go with the new mdx-bundler library made by the famous Kent C. Dodds.

AWS Lambda simplifies composable applications by offering serverless execution, seamless integration with AWS services, automatic scaling, and cost efficiency without the need to manage servers.

Deploying Dart functions to AWS Lambda enables you to utilize them not only within AWS Lambda but also integrate them with services like Amazon API Gateway, allowing you to leverage them in Flutter applications as well. This unified codebase in Dart offers great convenience.

Event Producers: Generate streams of events, which can be implemented using straightforward microservices with AWS Lambda (for serverless computing), Amazon DynamoDB Streams (to captures changes to DynamoDB tables in real-time), Amazon S3 Event Notifications (Notify when certain events occur in S3 buckets) or AWS Fargate (a serverless compute engine for containers).

Amazon Web Services (AWS) Lambda is a serverless function-as-a-service (FaaS) platform that lets you deploy, run, and scale code in the cloud as self-contained functions without having to manually configure any infrastructure. Lambda runs your functions on demand in response to specific events, such as an HTTP request from the internet or activity in another AWS service.

FaaS is specifically focused on building and running applications as a set of independent functions or microservices. Major cloud providers like AWS (Lambda), Microsoft Azure (Functions), and Google Cloud (Cloud Functions) offer FaaS platforms that allow developers to write and deploy individual functions without managing the underlying infrastructure.

So AWS Lambda is basically a serverless computing service that is offered by AWS. It enables developers to run the code in response to various events. It protects the developers from the pain of managing the servers. Using a serverless execution model helps the developers to handle provision, manage and scale the servers automatically. Through this approach the developers can fully focus on writing the code instead of dealing with other aspects.

The first product that popularized the term “serverless” was AWS Lambda, which is both the prototypical and archetypical function as a service provider. It also has a great name, which pings back to its envisioned place in the cloud of the future. In computer programming, a lambda, often referred to as a lambda function or lambda expression, is a concise way to represent an anonymous function, which is a function without a name. The concept originates from lambda calculus in mathematical logic and has been adopted by many programming languages, each with its own syntax and characteristics.

You can build a custom config rules in 2 ways, using AWS Lambda and CloudFormation Guard. Lambda gives you a lot of flexibility, but it also brings complexity of maintaining. CloudFormation Guard is a bit more lightweight in that regard. Yes, you still need to maintain the logic to determine when your resource is compliant or not. But you need to do this in both cases, thus my go to preference is CloudFormation Guard.

AWS Lambda: https://aws.amazon.com/lambda/