Prefect looks great, but it uses Prefect Community License for parts of it, that has an exclusion:
" Licensee is not granted the right to, and Licensee shall not, exercise the License for an Excluded Purpose. For purposes of this Agreement, "Excluded Purpose" includes, but is not limited to, using the Software, or any derivative works thereof, to make available any software-as-a-service, platform-as-a-service, infrastructure-as-a-service or other similar service that competes with Prefect products or services."
While I'm interested in using Prefect as part of SaaS I'm working on, I'm having trouble defining whether it would compete with their offering or not. In my SaaS Prefect UI will not be exposed, I need an ETL engine "behind the scenes" for parts of the whole workflow (some action, sends an event, and on that event a job is triggered).
In theory Prefect SaaS could be used to do the same, so I guess that would mean I'm competing with them?
On the other hand Flyte looks very young, that could mean it's not mature or hard to use for non-Lyft use cases.
Hi! Prefect CEO here. We made Prefect freely available for exactly this reason - so you can use Prefect and its UI to ensure that your business's processes are running smoothly. Broadly speaking, your internal use won't violate our license at all (unless your SaaS is a workflow orchestration platform, in which case please check out our open jobs because you're the sort of person we'd love to talk to :) ). If you have any questions at all, always happy to help.
Could you go more into this? How did you go about the evaluation and what metrics were you using? How did you capture the 'developers just hated it' in a way that leadership understood?
I'm not disputing the outcome, just feel like it would be useful for others in a similar situation.
Gonna second this. We are also in a situation where a few of the higher management were clearly bribed to push our company into Azure direction but the amount of problems we see may destroy our company..
I'm assuming that you run Kafka within AWS. Much of the hardware requirements/suggestions I've seen for Kafka are all for non-virtualized environments. If you can get into it, could you share some details...
- What is the size of your Kafka cluster
- What instances types do you use?
- Do you use EBS or use ephemeral storage?
- How much do you over-provision to deal with instance loss?
We're hiring all types (Analytics, UI, Test-Automation, Generalists) of developers and at all levels at the moment.
Responsibilities: What will I do?
* Looking for all levels of experience
* Contribute to the design and development of product features as well as major components
* Contribute to the innovation and evolution of the Spiceworks suite products
* Work directly with our growing community of over 2 Million IT pros as well as experience developers who are experts in the industry
Qualifications: What does it take to do this job?
* Looking for all levels of experience
* Object Oriented programming skills with Ruby-on-Rails ( Python or equivalent)
* Application and/or Web Application experience is a must
* Familiarity with HTML, CSS, JavaScript (Prototype) and Ruby-On-Rails
* Solving large-application/user-level problems, performance, scalability, etc.
* Skilled with distributed software (native or webapp)
* Some experience with SQL is desired
Email me at sajana @ spiceworks . com if you're interested!
---
Called the “Facebook of IT,” Spiceworks innovative model combines a network management app with an online community of over 2 million IT pros around the world. Our goal is to simplify “everything IT” by helping our users do their jobs, share tips and tricks, and connect with the tech vendors who sell them products. And, given we’re growing by over 2,000 users a day, it’s no wonder we’ve been called the “fast growing social business app” in history!
I have also been following this course and am extremely disappointed in its quality -- not just in poor production, but also in the coverage of course material. I would not recommend this as a primer on investing.
The approaches between the two campaigns relay the IT as a cost center vs a profit center debate. The Obama campaign used its technology to create a competitive edge while the Romney campaign minimized its internal operations and relied on outside parties which were not completely aligned with the goal of the campaign.
Also, I have a question which I would love to gain any insight on. In this article and others I've read about this , its been said that the Romney campaign could only start developing Orca after the primaries were finished. Why is this? Shouldn't the RNC have been in charge of developing something like this? Or are these applications very specific to the actual candidate?
I'm guessing that the party organization itself isn't allowed to do anything other than nominate their candidate. The campaign, of which the GOTV system is a part, has to be directed by the candidate. This makes sense in that you're technically electing a person, not a party.
