debezium-examples VS examples

There are a lot of great example here -> https://github.com/debezium/debezium-examples

I'm thinking about open sourcing the framework that I wrote to implement a managed saga inspired to the framework package in Debezium saga order-service: https://github.com/debezium/debezium-examples/tree/main/saga

Check out their examples repo: https://github.com/debezium/debezium-examples/tree/main/debezium-server-postgres-pubsub

Hi, I am struggling with debezium and elastic search the problem seems to be on the elasticsearch side or docker. I am using this example and when I try to create an index with mappings the return is (52) Empty reply from server. Even when I run es container according to es documentation and make curl -X GET "localhost:9200/_cat/nodes?v=true&pretty" request server returns an empty reply.

We have some Kafka Streams related examples in the debezium-examples repo, e.g. for FK joins, aggregations, and using a state store. They show usage of Kafka Streams in the context of CDC, but the same patterns are more generically applicable of course.

Well, it works with Postgres, but apparently not CloudSQL for PostgreSQL.

The original code for the connector context can be found here: https://github.com/debezium/debezium-examples/tree/master/end-to-end-demo/debezium-jdbc

To create a new Serverless service you can run the sls create command and pass a template as a parameter. You can see a list of template examples in the official sls repository. As I write this post, there isn’t a Django template available in this list. Therefore, we are going to create a serverless.yml file in the root directory of our project and manually write the code we need in it.

Here's an example that deploys a node lambda along with an api gateway with very minimal configuration (check out the serverless.yml).

serverless --template-url=https://github.com/serverless/examples/tree/v3/aws-node-scheduled-cron

If you are using Serverless Framework, it becomes slightly less obvious because these are logs being created for your function automatically. They are not defined in your Serverless.yml file. Let's run through an example using a simple HTTP serverless function source code: https://github.com/serverless/examples/tree/v3/aws-node-http-api.

Check this out

Here we’re still using the same Todo list example the folks at the Serverless Framework created as our codebase. But with some variations so that it more cleanly supports automated testing and the CICD toolchain used — AWS CodePipeline.

The lambda function was simple, convert this function into a Python function, then connect to a redshift database and do a table dump. Just enough to get a base going and eventually add more business logic to make it more complex. I completed the function exactly as requested and it ran successfully. Me "not being able to code out of a wet paper bag" was not the problem. I was literally 1 day late from Friday with the feature request and got cut on Tuesday.

Let’s consider a small application that uses two runtimes and provides two functions. This example will use Python and Node targeting AWS, but the concepts will be broadly applicable in other circumstances. The full the project files can be found here

I can’t wait to see what the serverless community builds with Ruby! When you make your first (or fifth) Ruby app, please do submit it to our Examples Repo and share it with the community.

You can find the full example project that we’ve been using in this GitHub repo. The easiest way to experiment with the project is to clone the repo and deploy it from your machine using npm run deploy.