When you say e2e, how big of the scope are you talking about? from frontend to everything in backend? can you give an example? I think the bigger the scope is, the more it will be used as a reference rather than directly able to use?
architecture of coderecipe: haha good question! yes we are using angular for frontend, and CMS is custom code built on top of AWS serverless.
If you are looking for more practical resources related to architectures in the cloud, you should take a look at https://coderecipe.ai . It is a dev community that allows others to share recipes (architecture + pros/cons/limitation/cost analysis + deployment instruction + source code) that can be used directly in real life situations.
If you have one or a few specific domain of architectures in mind, for example “how to do user management in AWS”, you can search for a collection of similar architectures like this https://coderecipe.ai/search?q=%23usermanagement , this way you can compare different alternatives. Similarly, if you are interested in different ways to “Store time series of data”, there’s also a collection of that here https://coderecipe.ai/search?q=%23timeseriesdb. The site contains a lot of recipes that is based on serverless design, so this will give you everything serverless related https://coderecipe.ai/search?q=%23serverless .
I am the founder of this platform, currently we have mostly AWS related recipes but there will be more GCP and Azure stuff coming soon, let me know if you have any questions :)
There seems to be multiple ways of storing time series data in AWS based on different requirements, but I always have a hard time finding them all. So, I decided to create a collection myself :)
Some of the resources are labelled as "Crosspost" meaning they are not full fledged code implementations as didn't get time to do that yet. Let me know if there's a specific "crosspost" resource you would like to see implemented or if I am missing anything!
I'm putting together a collection of short tutorials in the User Management/Authentication domain, when using AWS serverless. This covers both REST API and graphql endpoints, using AWS's in house Cognito User Pools or other 3rd party services such as Auth0. All of them are currently using serverless framework for deployment, and written in nodeJS, but there will be more suported infrastructure as code frameworks being supported soon (eg. terraform). This collection will be updated continuously to follow the newest best practice. Hopefully it will be helpful to you, and let me know if you have any questions!
Feel free to take a look at my code sample here with this new Data API on Aurora Serverless https://coderecipe.ai/architectures/77374273, demo and source code included. It removes the need of a vpc and it works like a charm
With this, VPC is no longer needed from lambda call to RDS, and this means that cold start time will be lowered from seconds to milliseconds. I made a ready to use recipe (source code+deployment script+demo included) here https://coderecipe.ai/architectures/77374273 hopefully this help others to easily onboard to this new API.
This is my first attempt gluing AWS's advance serverless platform with Google's advance Natural language API together. Traditionally creating a chatroom required a dedicated server that maintains and manages the websocket connection. API API Gateway's websocket API makes it easy so that you no longer need to do that. Any feedback would be greated appreciated!
Thanks for your feedback, in this post I made the assumption that the price of the cryptocurrency doesn't fluctuate automatically based on transaction volume, also I assume that AWS Aurora Serverless takes care of scaling problems such as max conns, etc. Therefore it can be achieve with such simple design. May I ask which part do you think I should dive deeper (overly simplify)? I will definitely improve it. Thank you for your time!
This is a basic crypto exchange, super simple version of Coinbase, for buying and selling cryptocurrencies such as Ethereum. I use AWS serverless to host the application code and handle blockchain transactions using web3.js, and storing transaction records in AWS Aurora Serverless with their new Data API. Any feedback would be greatly appreciated!!
Hey guys I recently found out Yelp's waitlist feature and found it quite useful, so I reverse engineer a super simple version of the system :) , do you think this is useful? Any comments will be super appreciated!
architecture of coderecipe: haha good question! yes we are using angular for frontend, and CMS is custom code built on top of AWS serverless.