Our great sponsors
-
goa
🌟 Goa: Elevate Go API development! 🚀 Streamlined design, automatic code generation, and seamless HTTP/gRPC support. ✨
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
But I think the benefits you get from many services (i.e. forced modularity) are well worth the small pains of managing multiple executables. (Much of that is solved by automation.) No matter if you are building a bigger service or many small ones, I would want it to be modular anyway. So there should be very little difference to the code. (My new fav famework forces network layering, so it's trivial to "decide later" if you are going to break up services or keep them in one binary. (Obvious disclaimers about drawing the dotted lines correctly apply.)
you can also go for Alpine.js instead of htmx, but it's the same principle. Alpine favors you slightly if you know some js, but that's not mandatory.