i am facing an issue with deploy and interaction with contract on Hyperledger Besu. I have created nodejs api to deploy any type of smart contract, and later interacting with deployed contract.Firstly i had deployed ERC20 contract to Besu network(besu quickstart)using web3.eth.Contracts.deploy method and interacted with same, everything works fine now for the second time when i deploy non-erc20 contract then i am unable to interact with erc20 contract functionalities but able to make calls to non-erc20 contract. Please suggest me resolution.
Need to know if the issue is with the Besu network or the nodejs apis i created
Related
I have created a Spring cloud microservices project with netflix APIs and a frontend with React. Now, I want to migrate this project to serverless using amazon web services with DynamoDB and cognito. Do you know, which steps should I follow to do that? And what should I consider before doing this migration? For the Frontend React I decided to use S3 to host it.
Be sure if u really want to do this . This will be a big project; almost like re-writing complete codebase. Good part is that lambda supports Java so u might end up doing lots of copy paste. You would have a lambda function of each REST api endpoint u were exposing.
I am trying to deploy a smart contract in remix, I have metamask and my eth balance should be enough (0.21ETH). But I cannot deploy the smart contract with no error display. What should I do.
There are some little configurations have to be set first, please check:
if your link is using http instead of https
if you have logged
in Metamask
if you have turned off the privacy mode in Metamask
I'm building an app and the idea is to go serverless.
I'm looking mainly at AWS and GCP (Google Cloud Platform), and as AWS costs are a bit obscure (at least for me), and there is no way to ensure not being billed, I'm going with GCP.
For the "server" part of the app, I would like to build an API on GCP as I could do with AWS API Gateway, but I couldn't find any matching product for that.
The closer one was Google Cloud Endpoint, but it seems to have a very different concept from AWS API Gateway. I've watched some videos about it (for example https://www.youtube.com/watch?v=bR9hEyZ9774), but still can't get the idea behind it or if it fits my needs.
Could someone please help clarify which GCP product would be suitable for creating an API and how it compares to AWS API Gateway?
Some link with info/example on how to do it would be really appreciated.
Google Product Manager here.
We don't have an exact analog for AWS API Gateway.
You're right about Cloud Endpoints. It's a bit of a different architecture than AWS uses -- it's a sidecar proxy that gets deployed with the backend. That's different than API Gateway, which is a fully managed proxy deployed in front of your backends.
If you are deploying in App Engine Flexible environments: good news! The Endpoints Proxy can be deployed as part of your deployment. It can do things similar to AWS API Gateway (API key validation, JWT validation, rate limiting).
We are working on some plans to allow for the proxy to be used in other places (Cloud Functions and the newer App Engine Standard runtimes).
And, finally: on our older App Engine Java and Python runtimes, we have API Frameworks that provide the same functionality. Those frameworks do the same thing as the proxy, but get expressed as code annotations and built into your app. We're moving away from the framework model in favor of the proxy model.
An example of springboot project with google cloud app engine can be found here-https://github.com/ashishkeshu/googlecloud-springboot
My use case is as follows,
I have built a rest api written in nodejs with serverless and when deployed will create lambdas and an api gateway that gives url which works fine. However, I will have multiple clients who would want to use this application (with their clients consuming the api) and I wouldn't want to duplicate the lambda's for each client as the business logic wouldn't change. What would be different is the stage variables set in the api gateway for each client.
Is there a way I can deploy and manage this using serverless, so that when a new client comes on board, I should be able to do something like update the serverless.yml with new api gateway details and then running the deploy command would generate the new gateway with it's own stage variables sharing the previously created lambdas.
Hope, the question is clear and apologies if this has been previously asked and answered.
I have 2 different modules, one is loyalty and another one is wallet. (both are written in java)
loyalty app is hosted on an AWS elastic beanstalk and I have an AWS API Gateway on top of it.
now I'm about to build the wallet and it will need to use some functionalities of loyalty module. I can put it under loyalty but it wouldn't make sense since they both server different purposes.
so I thought I would put wallet on another AWS elastic beanstalk with AWS API Gateway on top but then I wonder, if wallet wants to call loyalty to use any of its functions, how should it be done? I'm not sure if it's a good idea to call the API gateway on top of loyalty to access its functions. Or is it a correct way?
Whether it is a "correct" way depends on your architecture and design preferences. You can call one beanstalk application from another via API gateway, especially if you are calling public API methods, and one beanstalk application can call another directly (provided your subnets and security groups are set up to allow this (the default security group used set up by VPC does allow this)).
If you are intending to call private API methods in your loyalty app, then it would make sense to call the 'loyalty` app directly, because even assuming you have proper authentication controls on your API gateway methods it is even better for them to simply not be exposed to the public at all.
More generally, if the loyalty and wallet apps should be considered to be part of the same service, then I would put both under the same API gateway instance, and would allow wallet to call loyalty directly without going through API gateway.
I am not good at AWS, but by my understanding, your question sounds like your are mixing the deployment structure and source code structure. I think you can write shared source code for both, and deploy dlls(not dll in AWS?) seperately. I think it's not good to call API gateway.