News for hackers. Stuff that matters.
Re:Starting with microservices by jayd16 on Wednesday January 19, 2022 @05:08PM (#30000999)
Farming out libraries or subprojects to separate teams is an ok way to go as long as you don't mind a single language/build system. Its not as flexible but you maybe get some perf out of it.

You don't get the convenience of a single datastore with simple transactions but it sounds like you prefer the flexibility of services owning their own data.

As it turns out there's no silver bullet. Do what works for you.

Re:Starting with microservices by frozenport on Wednesday January 19, 2022 @05:44PM (#30001510)
>> single language/build system

Imagine designing your entire architecture around your build system.

Re:Starting with microservices by rgbrgb on Wednesday January 19, 2022 @06:06PM (#30001765)
If you're a startup, I think it's actually a pretty good design constraint. You're going to end up with a single system to optimize (inevitably in your 110% time because there's no platform team) and a leg-up in shipping with fast and well-tested infra (or at least better tested because it's what you're using everywhere else). Dropping-in and tweaking stuff across many parts of the system is way easier if it's consistent, easily testable wherever you are, and you know that tests for every dependency are being run on each PR.

On the opposite extreme you're talking multiple PRs, languages, test suites and deploys for every new feature. I've watched startups do this and die before finding something people want to buy.

Re:Starting with microservices by kitd on Thursday January 20, 2022 @05:53AM (#30007261)
It's not as stupid as you make it sound. It is after all how normal manufacturing works. What you build is constrained by your assembly line. If you want to build something new, start off with redesigning your assembly line. It's time well-invested that pays back in heaps later on.
Re:Starting with microservices by bob1029 on Thursday January 20, 2022 @06:28AM (#30007542)
> If you want to build something new, start off with redesigning your assembly line. It's time well-invested that pays back in heaps later on.

We applied this ideology to our software project. Our build/deploy toolchain is 100% in-house code. Turns out, there's actually not a lot of it required because you can build a monster .net project into a single exe distribution with 1 simple command line operation. This applies to most other ecosystems as well. Everything else is basic file operations and moving shit between computers. No reason to vendor either of these problems out.

The benefits of having bespoke CI tooling are difficult to overstate. We've got automated processes where a project manager can multiselect 20 different customers, select a commit hash, and schedule an email containing a link to a zip of the resulting build that will be delivered to each customer's configured IT contact upon completion - all with a single button press. This process also entails injection of customer-specific configuration that is pulled at runtime from another system into each customer's distribution. The email templates are configured on a per customer basis and email delivery is delayed based upon project parameters.

I can't imagine wiring something like this up in Jenkins or GH Actions.

Re:Starting with microservices by jayd16 on Thursday January 20, 2022 @11:41AM (#30011235)
Sounds like the only hard part is a nice interface to select the customer IDs. You can just pass along that data to select build configs or what have you.

How is the rest of the process not applicable to GH or Jenkins?