subscription-service | REST API service managing subscription pricing services | REST library

I'm getting all members that equal to name (e.g 'Malith) with their subscription products. That function is working 100%. Also with that output i'm try to return total records so front end can set paging, limit, offset easily. But i'm getting clone is not a function.

Below is my code

For our project we want to understand the Egress limits for sending events to configured subscribers in an Azure Event Grid. Looking at the documentation https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits it is not clear as to what is the egress limits in Event Grid ?

What is the difference between:

Publish rate for a custom topic (ingress) of 5,000 events per second per topic

And

Publish requests of 250 per second ?

Thanks

Let's say I am developing blog platform where users can register account, pay for subscription and create their own blogs. Platform consists of following microservices:

• account-service
• auth-service
• subscription-service
• blog-service
• api-gateway

I am thinking of implementing api-gw pattern where all microservices except api-gw will be deployed to private network (where they will be able to talk with each other directly either synchronically or asynchronically through message broker) and they will be publicly available only through api-gw.

There will be two clients/consumers of the API:

• frontend (for clients)
• cms (for admins)

Therefore I want to make use of separate-api-gw-per-client pattern, so actually there will be two api gateways, one for regular frontend (frontent-api-gw) and one for cms (cms-api-gw), but both will talk with same microservices.

My question is about authorization and where it should take place (or rather what are pros/cons for different approaches). Let's focus on two "endpoints":

1. frontend-api-gw::createBlog() => blog-service::createBlog()

Frontend api-gw exposes endpoint to create a new blog and this api call is "forwarded" to blog-service::createBlog() endpoint. Let's say that user is already authenticated (i.e. correct JWT with user id is passed along with request to api-gw).

The authorization that has to be made is to determine if user with this id can create new blog. This can be done by calling subscription-service to check if user has paid subscription. The main question is if this authorization should be made still on api-gw side (A) or on blog-service side (B):

1. cms-api-gw / frontend-api-gw::listBlogs() => blog-service::listBlogs()

Similar case - should userContext / JWT in any format be passed to each individual microservice and that microservice should decide what to return? Or individual microservices should not be aware of userContext (maybe only for logging purposes), rely on API GW authorization and just receive some parameters/arguments?

My thoughts:

In case A, the logic in each individual microservice is more complicated because of authorization layer. Can get more complicated where there will be more API gws, user roles etc. However API GW in this case is simpler and it only forwards requests to microservices.

In case B, the logic in each individual microservice is less complicated, simple and straightforward. However there is more logic in API GW because it has to implement authorization for all platform (at least for the part that this api gw is responsible for). Maybe it can be also advantage to have all authorization in one place and not spread across microservices?

Also in case B there is less coupling between individual microservices I think.

What do you guys think of those two approaches / maybe you have other "ideas"?

I was not able to find an answer to my question in the title. I suppose there is a limit. No information is listed for my question at https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits.

Example screenshot of Consumption plan showing a number of associated apps and slots:

According to documentation, there's a limit on deployment slots per App Service Plan, for example, for Standard is 5.

Is this limit for the whole Service Plan or is per Web Site in the Service Plan? I ask this because I have a Service Plan S1 with more than 5 web sites and each web app has 1 deployment slot, and it seems to work.

Trying to determine what the hard limits of Resources Types are within Resource Groups.

In our instance, we're specifically looking at the Resource Provider Microsoft.Network/publicIpAddresses.

The documentation states "Varies per resource type" but doesn't provide any additional details.

https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits

We are aware that the default limit is 800 resources but would like to know what the hard limit beyond this is.

Also reviewed the Azure Management REST API's and PowerShell Cmdlets but unable to locate any way of pulling this information programmatically.

I am having some trouble getting my dispatch.yaml file to run on the local devappserver. I have had two errors one seems to be related to indentation expecting , but found ? I can fix this by removing the indentation as shown below in my dispatch file.

The second problem happens when I have removed the indentation I get Unexpected attribute 'service' of type DispachInfoExternal I have tried copying the example from the google docs but I get the same error, I have also tried changing the name service to module as I believe that was the old name and I get the same error. I am using Atom as my editor.