Do you get a cut of any of that extra revenue?I managed to impress the C-Suite team with my recent application. This is the first time I have got direct exposure to C-Suite leadership for anything. I created a scoring algorithm application that rates accounts for their susceptibility to be upsold on various products we sell. Taking into account 129 datapoints that exist for a given account. This is something that the marketing/operations people theorized and they had a mock they were using with an excel formula. Reading about it I guess it's a common thing sales/operations people do I was pretty unfamiliar with the concept.
When I was tasked with it I added in a ton more factors that I indicated could be used. It was kind of cool but I struggle to call it an algorithm as it's a pretty basic system. The scope of it is just large. It is bearing fruit for the sales and operations people now and they're upselling accounts they did not even think would be receptive to it. Which is pretty cool.
When we do promotions/raises again in a few months. I already got a promotion and another raise (that I demanded) on top of that in the past like 8 months.Do you get a cut of any of that extra revenue?
Do you get a cut of any of that extra revenue?
Prob should grab a book on microservices and learn more.I really hate the term "microservices."
Let's make APIs that do exactly one call to do one thing and only one thing and this is somehow an innovation. I don't get it.
I really hate the term "microservices."
Let's make APIs that do exactly one call to do one thing and only one thing and this is somehow an innovation. I don't get it.
Aws server less api gateway on dotnet coreAnyone do API development? Trying to decide when to use an API gateway vs API proxy. Conflicting articles.. Requirement is pretty simple, just need a common API to sit in front of multiple microservices. Will offload authentication to API, maybe not ideal versus passing an auth token around to each service but it works for the requirements.
Don't need load balancing or anything fancy. Just a facade for microservice calls.
I mean... true mesh network is really different that plain Wifi (with an extender), unless I'm misunderstanding what you are assuming wifi means?This is just... how everything in the tech world is. It's like pretending Google Stadia and other video game streaming services are new when Sega Channel was a thing in 1994 or calling WiFi networks "mesh networks" and pretending it's new tech.
Depends on the company, but at Comcast and my current employer the presidents and VPs report to the CEO. We have various P/VP teams for various functional divisions of the company, and the guy at the top is CEO.What's the difference between the CEO and company President? We just hired a new President.
In our company, as the CEO explained, he hired the President (first we've ever had) to do the day to day for the company. As he feels it is better for him to spend all of his time on Strategy which the day to day was getting in the way of. The President reports to the CEO here.Not an MBA type person, so feel free to have someone tell me the real way, but my understanding:
CEO runs the company, the decisions, the reporting, etc
Company President is the same as the president of the board of directors, and is the one running the board (that the CEO reports into).
There are presidents/vice presidents depending on how the business is structured, like individual business units or etc. There will be other 'C' level executives, but (in theory) they should be the top of the line for that specific area, which ultimately falls under the CEO.
Unless you are at a bank, because then every fucker is a VP or AVP of something.
I honestly don't know too much about this, but I think a Gateway is useful if you'll have multiple clients talking to your API. I think a proxy is for decoupling the client's API from your backend API.Anyone do API development? Trying to decide when to use an API gateway vs API proxy. Conflicting articles.. Requirement is pretty simple, just need a common API to sit in front of multiple microservices. Will offload authentication to API, maybe not ideal versus passing an auth token around to each service but it works for the requirements.
Don't need load balancing or anything fancy. Just a facade for microservice calls.
Anyone do API development? Trying to decide when to use an API gateway vs API proxy. Conflicting articles.. Requirement is pretty simple, just need a common API to sit in front of multiple microservices. Will offload authentication to API, maybe not ideal versus passing an auth token around to each service but it works for the requirements.
Don't need load balancing or anything fancy. Just a facade for microservice calls.
Both (should) decouple front and back, gateway will usually be heavier and more feature rich. Do you have one in mind? We use Apigee, but I'd look at Zuul and just configure the parts you'd want to use. I'm not a developer so I don't know which of them is easier to use/build for.I honestly don't know too much about this, but I think a Gateway is useful if you'll have multiple clients talking to your API. I think a proxy is for decoupling the client's API from your backend API.
I assume this is a cloud-based app you're developing?