| |OCT - NOV 20258DOS AND DON'TS OF EXPOSING SERVICESBy Humberto Enríquez, Director of Software Engineering, ActinverAs technology evolves, it tends to recycle some concepts that are empowered by how they improve and find new ways of solving recurrent problems, making our lives easier. Exposing functionality through services is not a new concept, it has been cooking for a while, since RPC calls to SOA. It has been evolving to simplify how we can connect systems, regardless of the technology they are built in. More recently, we are connecting companies through APIs, offering not only specific information as traditional integration would do, but moreover, providing full services such as: creating a banking account, see maps real time, integrating social network services and so on and so forth.Here is a quick list of what in my experience you should and shouldn't do if you want to go down the road of exposing services, either internally or outside your organisation.Build an ArchitectureDesign and build an architecture where your services will be living, regardless of if you are going for an API led connectivity, API gateways or just microservices, will surely save you some headaches in the future. At first, architectures might seem like they take quite some time, but it is time well spent. A properly defined architecture will help you put things where they belong and more importantly, everyone working with the architecture will know where to put them, instead of just developing as you go basis. Make it scalable ­ Be sure to design an architecture that will cope with growth and the load expected by the business. It must perform ­ Its great if your design escalates, but it takes a lot out of it if it is slow, it must be quick and keep it that way when it grows. Designs commonly fail due to lagging IN MY OPINION
< Page 7 | Page 9 >