I have a question along similar is this
I have a question along similar "is this a good idea" lines: is it sane to use windmill as a comprehensive solution for your application's API, webhooks, DB/data backups, etc?
I'm looking at this project I'm on and unsure of why that would be a bad idea. I have lots of scheduled things to worry about, webhooks, and so on. I need to work with multiple languages, but don't want to deal with multiple services or deployments. Having internal apps to help less technical people manage data eventually would be icing on top. Do you know if people are using windmill to that extent, or do you often run into snags where a traditional code base would be preferable?
1 Reply
I can see how being "boxed in" by windmill in some scenarios might be an issue, but honestly... Sometimes that's more of a blessing than a curse in software 😂