• 0 Posts
  • 2 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle
  • We had about 10-15 lambda “Microservices” each of these packaged up a service/contracts library to be consumed by other services that used them. We also had an MVC API and a few windows services that were built for a “distributed monolith”.

    We built all all branches on every push, we tried to deploy updates multiple times a week.

    We had 4 devs working on .net

    The main thing with sleet is that I made zero effort to prune anything from the feed, so eventually it might cost a few dollars per month for S3 storage, but it was literally zero maintenance after we got it set up.


  • At my last job, we used sleet in combination with S3 and a cloudfront distribution with an authorization lambda for pulling packages. I think the whole setup took about 2 hours and it was rock solid.

    This was necessary because we were using Octopus Deploy and were bumping into storage limits with their built in feed.

    We were a relatively small team, and relatively slow package publish rate (10x a day, probably).

    Biggest issue with sleet is that it’s not going to support “pull through” so you’ll need to have multiple nuget feeds configured.