Hi everybody, I want you to meet another great team using SST. Henry Schein One is the world’s largest dental practice management software company. And they are using SST and Seed to build the patient booking experience. In this post I spoke to @Jack Fraser and @Phil Astle about their experience with SST: https://serverless-stack.com/blog/henry-schein-one-the-worlds-largest-dental-practice-management-software-company-is-building-with-sst.html They are also hiring, so check out their job opportunities here: https://dentr.co.uk/jobs

Would love to see more real world shop talk. This is great but I want to hear the nitty gritty details and learnings they had using SST and Seed. The small tips and tricks they use to make DX easier.

after 9 months with sst at canopy, with an engineering team of about 12+ and growing, we've encountered quite a few pains too! most of them pertains to CDK and AWS itself though, and not SST itself. we love sst, but here's a few pain points, 1. changing resources shared among different stacks often lead to some orphan export value that's suck. sometimes this means we have to jump into cfn to remove values manually, or find a workaround 2. we moved off seed to github actions to move away from git-branch based deployment. deployment became a bit slower but now we can have manual approval checks to deploy to different stages instead of relying on merges b/t branches 3. setting a unique stage per developer was a problem that we made a customer solution to solve, but i think sst solves it now? fun story: i accidentally almost took out our entire infrastructure like an idiot because i clicked delete app + resources in Seed. thought it was still clicking thruogh a stage only haha.

@Tharshan it’s not all plain sailing but the power it has given us has been good. See comments and threads that myself or @Phil Astle have posted on the #sst channel for any issues we have come across. Most have been solved very quickly by the likes of @thdxr and @Frank 😃

we needed a more comprehensive pipeline in addition to having the manual checkpoints.

These are great pieces of feedback @Dennis Dang! Really appreciate you sharing them. I think for #1 we’d want to take a crack at it. @Frank might have more to share but I think CDK tried to fix it but scrapped their implementation. For #2, we’ll be sharing more about our Seed roadmap soon. We first want to make sure it’s integrated with SST well. For #3, yeah that’s something @thdxr fixed and wrote about here: https://docs.serverless-stack.com/working-with-your-team

That's right, and building real world applications with it.

Yeah I think it might be worth doing a deep dive on some real world architectures.