I'm a web, database, and network architect based in NYC, with specializations in the financial services, publishing, and SaaS sectors.
I build complex Marketo integrations for companies large and small... and can make Marketo forms and emails do things you never thought possible!
Check out my blog at https://blog.teknkl.com, which has Marketo-specific technical insights you won't see anywhere else, along with wider topics from my programming and systems work.
Sean did say "translate," though.Every Velocity task can be done in JS, but *not* vice versa by a long shot. So I wouldn't be pessimistic about translating in the direction.Sean, i...
True... we build this stuff a lot, so I think tech effort isn't a stopper but simply a project description. We have a webhook engine that's already load-balanced/cloud-hosted and a...
This is a common problem with a simple and complete solution (sorry Greg, no email is necessary).Save the Munchkin cookie to a SFDC custom field. When the lead syncs over to Market...
Surely the people making guarantees about consistency + concurrency weren't core architects, though? Seems kind of weird to me, honestly, that Marketo would be sold as an API-first...
Hey, I didn't say "static sharding"! Any (request) sharding architecture must take availability into account. Rerouting in response to runtime conditions would have no ill effect h...
I think of this not as a Munchkin (Visit Web Page) issue but a click tracking (Click Email) issue.For Munchkin, it's fixable by stripping off unwanted query params before running M...
+1 to everything Greg said. The maximum possible height of the form including visibility rules is not computed. It would be impossible for Marketo to do this on the server, in any ...
You don't have to serialize, but use a sharding algorithm so updates for the same lead are processed by the same worker. There's no utility to attempting parallel upserts of the sa...