It seems that Dark is designed to allow you to wrap external APIs in easy-to-use interfaces, so it should be at home as part of a larger SOA or ecosystem, of course with the caveat that it's still being developed. See the footnote at https://medium.com/darklang/dark-residency-7dbc878a5f0a .
Yes, that's exactly right. Dark speaks HTTP (and at some point, will speak GRPC, Thrift, etc) so you can access 3rd party services over HTTP (and wrap them in SDKs in the Dark package manager, same as on npm).
We expect we'll have some built-in support for common things (resizing images and videos, or generating pdfs for instance; we already support static assets on a CDN).
Re:How Dark Deploys Code in 50ms
by simonebrunozzi on Thursday July 11, 2019 @01:17PM
(#20413390)
Hey Paul, nice to see you here on HN. Very promising start!
What's the best way to contact you? (I'm $HNusername @ gmail).
Thank you! I'm at https://twitter.com/paulbiggar or [email protected].
Re:How Dark Deploys Code in 50ms
by stevefan1999 on Thursday July 11, 2019 @08:49AM
(#20411074)
hence the pun "going Dark", you're complete shut-in into a vendor-specific environment
One thing that I notice is that Dark requires a completely walled in environment to be able to deliver all of its promises. In reality, any real-life project has to interact with external services, legacy systems, or custom peripherals which are unlikely to be based on Dark.
How will Dark be able to handle such cases? Current tooling and processes are able to cope with such things through custom, hand-crafted, and as the article stated, often fragile, systems and processes. The are a pain, but they get the job done. They are very versatile by their nature. While they break more often that we would like to, they can be patched up well enough to band-aid over rough patches and adjust to surprising externalities. Dark seems to have one way of doing things, and I am curious how compatible that way is when it comes to interfacing with external systems.